Summary: | a libX11 Makefile overrides CC variable | ||
---|---|---|---|
Product: | xorg | Reporter: | J.P. Larocque <piranha-fdo-bz> |
Component: | Lib/Xlib | Assignee: | Jim Gettys <jg> |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | high | CC: | astrand, pb |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
J.P. Larocque
2004-02-02 10:01:11 UTC
Phil, I believe this is your doing. I know we talked about it once. What is the correct fix? Yes, this was indeed my doing. The issue here is that, when cross-compiling, the stuff in the "util" directory needs to be built with the host compiler rather than the target one. I gather from the autotools people that, with a sufficiently new version of automake, writing "host_PROGRAM" in the Makefile.am ought to cause everything to just work. I'll try this out and see if it does the right thing; if so, the offending override of CC can certainly be removed. Well, we already depend on some pretty recent versions of tools; if we have to update one more, so be it. This BUG bites me once more while crosscompiling (add to PTXdist) Maybe the following patch is a acceptable workaraound: diff -ruN libX11-0.99.0.orig/src/util/Makefile.am libX11-0.99.0/src/util/Makefil e.am --- libX11-0.99.0.orig/src/util/Makefile.am 2005-08-01 22:15:26.000000000 +0 200 +++ libX11-0.99.0/src/util/Makefile.am 2005-10-10 01:00:38.836860355 +0200 @@ -1,8 +1,12 @@ # $XdotOrg$ -noinst_PROGRAMS=makekeys +# evil hack +AM_CFLAGS=$(CFLAGS_FOR_BUILD) +AM_LDFLAGS=$(LDFLAGS_FOR_BUILD) + +CC=$(CC_FOR_BUILD) +LIBTOOL = @LIBTOOL@ --tag=CC -makekeys_CFLAGS=$(X11_CFLAGS) $(BIGREQS_CFLAGS) +noinst_PROGRAMS=makekeys -#override CC = gcc -LINK = $(CC) $(AM_CFLAGS) $(CFLAGS) $(AM_LDFLAGS) $(LDFLAGS) -o $@ +# makekeys_CFLAGS=$(X11_CFLAGS) $(BIGREQS_CFLAGS) This was fixed at some point since I know it works for me. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.