Summary: | GCC fails to rebuild itself with multilib enabled | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | kevin <kacarter> |
Component: | [OLD] Core system | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED INVALID | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
kevin
2004-04-23 11:14:36 UTC
EDIT: This is what I should have said: The problem seems to be that gcc will build successfully /initially/ with multilib enabled but fails to rebuild itself afterwards with multilib enabled. can you cat /usr/lib/libc.so and give us the output? or attach it to the bug? it seems that during the process of upgrade you might have upgraded the 32bit umul libs to a new version, which may be responsible for your problem and explain why gcc was able to compile the first time. As per request: weakest-link / # cat /usr/lib/libc.so /* GNU ld script Use the shared library, but some functions are only in the static library, so try that secondarily. */ OUTPUT_FORMAT(elf64-x86-64) GROUP ( /lib/libc.so.6 /usr/lib/libc_nonshared.a ) Please compare the follwoing output with that you get on your system: phi chroot # cat /usr/lib32/libc.so /* GNU ld script Use the shared library, but some functions are only in the static library, so try that secondarily. */ OUTPUT_FORMAT(elf32-i386) GROUP ( /lib32/libc.so.6 /usr/lib32/libc_nonshared.a ) If it differs from mine (/lib/ instead /lib32/, you have to blame me (welcome to the club ;-) and remerge app-emulation/emul-linux-x86-baselibs-1.1. app-emulation/emul-linux- I noticed that it failed even without multilib in my USE flags just recently, so I'm going to test out a theory. I'll post the results after Itest it. Well, it appears that -ftracer is what broke everything. I rebuilt everything without -ftracer and it all worked. Someone suggested that it might have been binutils that was breaking with the aggressive optimizations, so this may warrent some further looking in to. i'd say that the mix of -O3 and -ftracer broke it. -ftracer is incredibly safe when used with -O2, i have it in my CFLAGS and never has anything broken. |