Re: gcc-3.4 build failure on hurd-i386
On Mon, May 02, 2005 at 06:09:04PM +0200, Matthias Klose wrote:
> - which is the last version that built on hurd-i386?
According to ftp.debian.org, it appears to be 3.4.1-7, though I do not
> - does gcc-4.0 (experimental) build?
No, at least not out of the box. libffi needs to get disabled (it
claims to not having been ported yet), and I think there was some other
issue (perhaps just some additional Build-Depends not available).
Anyway, back to the gcc-3.4 build log:
> ./xgcc -B./ -B/usr/i586-gnu/bin/ -isystem /usr/i586-gnu/include
> -isystem /usr/i586-gnu/sys-include
> -L/build/mbanck/gcc-3.4-3.4.3/build/gcc/../ld -O2 -DIN_GCC -W
> -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes
> -Wold-style-definition -isystem ./include -I. -I. -I../../src/gcc
> -I../../src/gcc/. -I../../src/gcc/../include -g0
> -finhibit-size-directive -fno-inline-functions -fno-exceptions
> -fno-zero-initialized-in-bss -fno-unit-at-a-time \
> -c ../../src/gcc/crtstuff.c -DCRT_BEGIN \
> -o crtbegin.o
> In file included from ../../src/gcc/crtstuff.c:62:
> ../../src/gcc/tsystem.h:79:19: stdio.h: No such file or directory
I see now: /include appears to be hard-coded as the sole system include
search path for *-gnu-*, while my system has a real /usr and thus no
/include directory. If I link /usr/include to /, it builds fine (well
crtbegin.o at least).
Debian GNU/Hurd is (currently) trying to support both a real /usr and a
/usr->. symlink (the install CDs make a symlink, but crosshurd users can
choose), so I wonder what the right fix is, perhaps remove whatever
special policy enforcement there is for /include for Debian only?
What do the other Hurd porters think?