| Summary: | emerge of any package fails with a gcc segfault | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sarath Menon <sm> |
| Component: | New packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED FIXED | ||
| Severity: | critical | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Preprocessor output during the segfault. | ||
|
Description
Sarath Menon
2005-06-24 02:10:43 UTC
Created attachment 61830 [details]
Preprocessor output during the segfault.
This is the preprocessor output that I got during the compile of glibc
Oh, I must be getting old, i forgot to mention which package i was trying to emerge now ;). The whole output that i have posted including the preprocessor output is what i got during a "emerge glibc", because after reading past bugs, some other problems were solved by it. Folks, Here is some additional info to debug it further. I have poked around the files that cause the ICE and found that gcc segfaults only when -O2, -O1 or -O3 optimizations are passed. I tried with a couple of files, and found that -0[1-3] flags are also good to go. I tried compiling glibc and gcc without this flag to see if I could get a working configuration and saw that all configure scripts want to pass -O2 as standard to the Makefile. In fact glibc refuses to compile without any optimizations and gcc takes -O2 as a CFLAG even if I don't set it. Is this behaviour due to the ebuild? I dont think the vanilla versions of either one will make this modification. Well, I fixed the issue myself. I build gcc using ./configure, make make install - this time keeping very sane CFLAGS. The build went fine, and this one was able to accept all my old CFLAGS. I have since recompiled glibc (just to be on the safe side) and have tested that my gcc is now able to compile stuff like it used to do. Please close this bug, unless you have an explanation for what happened and steps/patches to fix it. I doubt this being the case, then again, it could be because I did not have nptl support in glibc(I have enabled it now). Iam not sure about it, so I leave it to you guys. The user resolved the issue already, see the previous comment. |