------- Comment #7 from thunderwolf66102 at yahoo dot com 2010-02-01 08:49
-------
Under Gentoo, GCC x86_64-pc-linux-gnu-4.4.2 appears to also build a broken
glibc 2.9. I have tried many times over the past several days to build and
install gentoo's 2.9_p20081201-r3 to replace a previous 2.9_p20081201-r2.
After installing the new glibc several binaries would break - among them being
python, squid and init. Other binaries worked fine.
The first luck I had was I created a fresh environment under a chroot, built
glibc, and copied it over. Tried to build 2.9_p20081201-r3 and install again
after this with the same problems. I looked at a couple of other computers
that I have and noticed their default compilers were all set to 4.3.x.
Switched to 4.3.4 on the problem system, built 2.9_p20081201-r3 and installed
again with no issues.
One of the files related to the segfaults appeared to be libm-2.9.so.
Replacing this file with the backed up -r2 version restored python.
I believe this has also happened once before though at that point I simply
backed up the system, nuked, and reinstalled. Python was broken then as well.
flags = -O2 -finline-functions -mtune=athlon64 -march=x86-64
-fomit-frame-pointer -mfpmath=sse,387 -pipe -msse3
--
thunderwolf66102 at yahoo dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |thunderwolf66102 at yahoo
| |dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39852
