On Tue, 2011-08-23 at 02:41 +0200, Samuel Thibault wrote:
> Package: emacs23
> Version: 23.3+1-1
> Severity: serious
> Justification: FTBFS
>
> Hello,
>
> emacs23 currently FTBFS on any-i386, because gcc #defines i386 to 1,
> which gets in the way of include paths: see attached log, in particular
>
...
>
> Notice this:
>
> -I/usr/include/dbus-1.0 -I/usr/lib/1 -linux-gnu/dbus-1.0/include
>
> configure.in talks about such issue:
>
> # Now get this: Some word that is part of the ${srcdir} directory name
> # or the ${configuration} value might, just might, happen to be an
> # identifier like `sun4' or `i386' or something, and be predefined by
> # the C preprocessor to some helpful value like 1, or maybe the empty
> # string. Needless to say consequent macro substitutions are less
> # than conducive to the makefile finding the correct directory.
> [cpp_undefs="`echo $srcdir $configuration $canonical unix |
> sed -e 's/[^a-zA-Z0-9_]/ /g' -e 's/^/ /' -e 's/ *$//' \
> -e 's/ */ -U/g' -e 's/-U[0-9][^ ]*//g'`"]
>
> So probably more hack is needed...
>
> (yes, the attach log actually fails on some other error, already
> reported as #629567, but the path issue will bring others once #629567
> is fixed)
So the problem is due to gcc?
My investigation shows that config.log and config.status shows the
correct paths:
configure:8438: checking DBUS_CFLAGS
configure:8441: result: -I/usr/include/dbus-1.0
-I/usr/lib/i386-gnu/dbus-1.0/include
but the generated Makefiles are wrong:
build-{x,nox,lucid}/src/Makefile
DBUS_CFLAGS = -I/usr/include/dbus-1.0 -I/usr/lib/1 -gnu/dbus-1.0/include
*/src/Makefile.c has the correct patch though!
DBUS_CFLAGS = -I/usr/include/dbus-1.0
-I/usr/lib/i386-gnu/dbus-1.0/include
In which order are makefiles generated:
Makefile.in->Makefile.c->Makefile?
Is gcc is involved from Makefile.c to Makefile??
Links to documentation??
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
