all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
Cc: rich@phekda.freeserve.co.uk
Subject: Re: Emacs CVS & DJGPP CVS: "make bootstrap" fails
Date: Sat, 18 Jan 2003 13:25:30 +0100 (MET)	[thread overview]
Message-ID: <200301181320.h0IDKqDU011701@stubby.bodenonline.com> (raw)
In-Reply-To: <2110-Sat18Jan2003132358+0200-eliz@is.elta.co.il> from "Eli Zaretskii" at jan 18, 2003 01:23:59

> 
> > Date: Thu, 16 Jan 2003 19:50:44 +0000
> > From: Richard Dawe <rich@phekda.freeserve.co.uk>
> > 
> > xmenu.o: In function `_Fx_popup_menu':
> > xmenu.c:738: undefined reference to `_DefaultRootWindow'
> > xmenu.c(.text+0x1010): undefined reference to `_XQueryPointer'
> > xmenu.c:761: undefined reference to `_FRAME_OUTER_TO_INNER_DIFF_X'
> > xmenu.c:763: undefined reference to `_FRAME_OUTER_TO_INNER_DIFF_Y'
> > collect2: ld returned 1 exit status
> > make.exe[1]: *** [temacs] Error 1
> 
> The DJGPP port uses the non-toolkit part of xmenu.c (to emulate X
> menus).  For this to work, any X-specific stuff in that part of xmenu
> should be either (1) emulated by the code in msdos.c/msdos.h, or (2)
> defined away in msdos.h, or (3) defined in msdos.h to some innocent
> replacements (like "typedef int XFooBar" or some such).
> 
> I'm guessing that some recent changes violated this arrangement.

Yes, I did that.  I checked when HAVE_MENUS gets defined, but it
did not occur to me that a file in s/ (s/msdos.h) might define it.

I'm guessing DJGPP does not use configure?

	Jan D.

  reply	other threads:[~2003-01-18 12:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3E270D14.6DE95026@phekda.freeserve.co.uk>
2003-01-18 10:23 ` Emacs CVS & DJGPP CVS: "make bootstrap" fails Eli Zaretskii
2003-01-18 12:25   ` Jan D. [this message]
2003-01-18 12:53     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200301181320.h0IDKqDU011701@stubby.bodenonline.com \
    --to=jan.h.d@swipnet.se \
    --cc=rich@phekda.freeserve.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.