Compiling glibc-2.3.2 (-2.3.3?) snapshot 20031115 with gcc-3.4 snapshot 20031119
Robert Moss
robert.moss@jesus.ox.ac.uk
Mon Nov 24 15:08:00 GMT 2003
Hi,
It appears that this is sadly completely knackered - as is compiling
*any* glibc 2.3.2 release or snapshot. The compile dies as soon as
elf/ld.so is used for the first time, with the following error:
CPP='gcc -E -x c-header'
/var/tmp/portage/glibc-2.3.2-r9/work/glibc-2.3.2/buildhere/elf/ld-linux.so.2
--library-path
/var/tmp/portage/glibc-2.3.2-r9/work/glibc-2.3.2/buildhere:/var/tmp/portage/glibc-2.3.2-r9/work/glibc-2.3.2/buildhere/math:/var/tmp/portage/glibc-2.3.2-r9/work/glibc-2.3.2/buildhere/elf:/var/tmp/portage/glibc-2.3.2-r9/work/glibc-2.3.2/buildhere/dlfcn:/var/tmp/portage/glibc-2.3.2-r9/work/glibc-2.3.2/buildhere/nss:/var/tmp/portage/glibc-2.3.2-r9/work/glibc-2.3.2/buildhere/nis:/var/tmp/portage/glibc-2.3.2-r9/work/glibc-2.3.2/buildhere/rt:/var/tmp/portage/glibc-2.3.2-r9/work/glibc-2.3.2/buildhere/resolv:/var/tmp/portage/glibc-2.3.2-r9/work/glibc-2.3.2/buildhere/crypt:/var/tmp/portage/glibc-2.3.2-r9/work/glibc-2.3.2/buildhere/nptl
/var/tmp/portage/glibc-2.3.2-r9/work/glibc-2.3.2/buildhere/sunrpc/rpcgen
-Y ../scripts -c rpcsvc/bootparam_prot.x -o
/var/tmp/portage/glibc-2.3.2-r9/work/glibc-2.3.2/buildhere/sunrpc/xbootparam_prot.T
make[2]: ***
[/var/tmp/portage/glibc-2.3.2-r9/work/glibc-2.3.2/buildhere/sunrpc/xbootparam_prot.stmp]
Segmentation fault
make[2]: Leaving directory
`/var/tmp/portage/glibc-2.3.2-r9/work/glibc-2.3.2/sunrpc'
make[1]: *** [sunrpc/others] Error 2
make[1]: Leaving directory
`/var/tmp/portage/glibc-2.3.2-r9/work/glibc-2.3.2'
make: *** [all] Error 2
Obviously, strace elf/ld.so isn't much help:
execve("./ld.so", ["./ld.so"], [/* 33 vars */]) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Now, I'm not going to put an entire objdump -Dr elf/ld.so into an e-mail
as that would just be plain rude, so instead, the very same file is
available here:
http://home.jesus.ox.ac.uk/~rmoss/ld.so
This has - I *think* - received some discussion before:
http://gcc.gnu.org/ml/gcc/2003-01/msg00069.html
and was apparently fixed, but speaking to Andreas it appears that this
didn't actually work.
Now, clearly, with this being the upcoming stable compiler, it would be
nice if there was at least a patch knocking about for glibc that allowed
it to compile with GCC 3.4. I've heard things about trying to use
no-z-defs=yes, but to be quite honest, I'm not really sure what they're
on about (I'm no glibc hacker!), and looking through all the sources for
indications of z-defs shows that everything that appears to want it set
already has it set to yes. I may be wrong, though. The compile was done
with CFLAGS="-O" to prevent other errors that stopped the build getting
even this far.
Can anyone help? I'm hoping to get a patch submitted to Gentoo Linux's
glibc maintainer early, in the hope that we can manage to get a glibc
build that works with any currently supported (currently 3.2 and 3.3)
*and* unsupported (3.4) GCC release.
If any more information is required, please don't hesitate to ask.
Many thanks in advance,
Rob Moss
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 264 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20031124/773e2850/attachment.sig>
More information about the Libc-alpha
mailing list