From: Eli Zaretskii <eliz@gnu.org>
To: stephen.berman@gmx.net
Cc: emacs-devel@gnu.org
Subject: Re: build failure [Re: bug#17673: 24.4.50; trunk r117239 build failure on Windows]
Date: Tue, 03 Jun 2014 19:13:16 +0300 [thread overview]
Message-ID: <83wqcy7yzn.fsf@gnu.org> (raw)
In-Reply-To: <83y4xe7ze3.fsf@gnu.org>
> Date: Tue, 03 Jun 2014 19:04:36 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: emacs-devel@gnu.org
>
> > From: Stephen Berman <stephen.berman@gmx.net>
> > Date: Tue, 03 Jun 2014 17:11:48 +0200
> >
> > >> In file included from ../../src/menu.h:25:0,
> > >> from ../../src/menu.c:52:
> > >> ../../src/../lwlib/lwlib.h:24:27: fatal error: X11/Intrinsic.h: No such
> > >> file or directory
> > >> compilation terminated.
> > >> make[1]: *** [menu.o] Error 1
> > >
> > > Should be fixed now.
> >
> > I get the same error bootstrapping GNU/Linux from trunk bzr 117248,
> > i.e. after your fix.
>
> I fixed it only for MS-Windows.
>
> > My system:
> >
> > x86_64-suse-linux-gnu, GTK+ Version 3.10.4
> > Windowing system distributor `The X.Org Foundation', version 11.0.11403901
> > System Description: openSUSE 13.1 (Bottle) (x86_64)
> >
> > Configured using:
> > `configure --without-toolkit-scroll-bars CFLAGS=-g3'
>
> That would mean you don't have X11 headers on that system installed?
> How's that possible?
FWIW, I've just compiled the current trunk on a x86_64 Trisquel
GNU/Linux with GTK-2.0, and saw no warnings or errors.
next prev parent reply other threads:[~2014-06-03 16:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 15:11 build failure [Re: bug#17673: 24.4.50; trunk r117239 build failure on Windows] Stephen Berman
2014-06-03 16:04 ` Eli Zaretskii
2014-06-03 16:13 ` Eli Zaretskii [this message]
2014-06-03 16:41 ` Stephen Berman
2014-06-03 17:02 ` Eli Zaretskii
2014-06-03 17:13 ` Eli Zaretskii
2014-06-03 17:24 ` Dmitry Antipov
2014-06-03 17:29 ` Dmitry Antipov
2014-06-03 17:52 ` Glenn Morris
2014-06-03 18:16 ` Dmitry Antipov
2014-06-03 18:51 ` Stephen Berman
2014-06-03 20:02 ` Paul Eggert
2014-06-03 21:02 ` Eli Zaretskii
2014-06-03 21:12 ` Stephen Berman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wqcy7yzn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stephen.berman@gmx.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).