Re: libX11-6.2.1 can't find keysymdef.h, and gmake needed
"Jeremy C. Reed" <[email protected]> Wed, 26 Nov 2003 17:30:05 -0800 (PST)
| Newsgroups | gmane.comp.freedesktop.xlibs.general |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 26 Nov 2003, Jamey Sharp wrote: > On 11/26 03:05PM, Jeremy C. Reed wrote: > > My fix for libX11 was to patch configure: > > # > > -KEYSYMDEF="" > > for flag in $X11_CFLAGS; do > > Um... I changed X11_CFLAGS to XPROTO_CFLAGS on 2003/11/13, because I ran > into a problem much like this. Have you updated from CVS since then, and > re-run autoconf? No. I am using the tar sets as available from http://freedesktop.org/~xlibs/dist (I need to use download files because they are used by an automated build system that doesn't easily support using CVS to fetch code.) > I guess you have an additional problem though. It looks like pkg-config > omits /usr/include from output for --cflags. (I suppose nobody > previously had trouble because everbody wanted to install in > /usr/local/include.) The right patch to configure.ac probably makes the > loop read: > > for flag in /usr/include $XPROTO_CFLAGS; do Okay that worked (with s,/usr/include,-I/usr/include,). Thanks. > > "/scratch/pkgsrc/new/libX11/work.puget/libX11-6.2.1/src/util/Makefile" > > line 472: Need an operator > > bmake: Fatal errors encountered -- cannot continue > > It looks like the line in question is "override CC = gcc". (In the > future, please include lines referenced by errors; the Makefiles are > auto-generated, after all, and might be different for you than me) I can > believe that "override" is a GNU make extension, though `info make` > doesn't say that it is. Sorry, forgot to include that context. Yes, it was that line: override CC = gcc <-- this is line 472 # Tell versions [3.59,3.63) of GNU make to not export all variables. # Otherwise a system limit (for SysV at least) may be exceeded. .NOEXPORT: Maybe later I will try making it bmake friendly. > It's been suggested that makekeys should be translated into some > scripting language (e.g. Python or Perl) so that we don't have to think > about cross-compiling most of Xlib and then natively compiling makekeys. I don't know about this. I guess I can look in archives. Jeremy C. Reed http://www.reedmedia.net/