Summary: | glibc-2.4-r4 failed to compile (segfault @ xbootparam_prot.stmp) with -Wl,--export-dynamic | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stefan Struhs <mail> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Stefan Struhs
2007-01-03 00:44:10 UTC
the thing is with that error, it could be caused by many things ... the only thing it tells you is that the glibc failed to compile properly build it up with debugging enabled and throw gdb at the process (In reply to comment #1) > the thing is with that error, it could be caused by many things ... the only > thing it tells you is that the glibc failed to compile properly > > build it up with debugging enabled and throw gdb at the process > Hi, changed /etc/make.conf as follows: 1. added -g and -ggdb to CFLAGS 2. added debug to USE 3. added nostrip and splitdebug to FEATURES Tried to gdb --arg /usr/bin/emerge `-1 linux-headers binutils gcc glibc` and then run produced the following error: Starting program: No executable file specified. Use the "file" or "exec-file" command. How can I "throw gdb at the process" if I can't run emerge with gdb? Thanks in advance! Regards, Stefan Struhs (In reply to comment #1) > the thing is with that error, it could be caused by many things ... the only > thing it tells you is that the glibc failed to compile properly > > build it up with debugging enabled and throw gdb at the process > The thing with this bug is that it seems that LDFLAGS="-Wl,--export-dynamic" (see emerge --info) does not work with all versions of glibc according to as thread on forums.gentoo.org. Removing LDFLAGS from make.conf solved the problem. In addition I was able to enhance my CFLAGS. Anyhow, I think it is a bug in the ebuild or make file (don't know where exactly). You should at least give a warning about using a user defined LDFLAGS or better about this special LDFLAG. Regards, Stefan Struhs sorry, didnt see you had custom LDFLAGS ... there's absolutely no reason at all you should be enabling that globally on your system, so remove it |