Summary: | [4.1/build] fails to build on i[3-5]86 with -g | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Loz Hygate <gentoo> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gentoo, glynn, loki_val, mg, v.savin |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | http://gcc.gnu.org/PR22313 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 155417 | ||
Attachments: | gcc41-pr22313.patch |
Description
Loz Hygate
2006-06-27 03:00:59 UTC
and it fails to emerge at the same place everytime ? I've only tried it twice (takes a very long time to build on this machine). It failed at the same place both times. I did an emerge sync and emerge -u world at the weekend. This installed a new version of binutils, but the gcc build failed at the same place. Probably a red herring but http://kernelslacker.livejournal.com/44342.html could be relevant. gcc-3.4.6-r2 is the latest version of gcc that I've managed to build. This looks a lot more like it: http://gcc.gnu.org/ml/gcc-bugs/2006-01/msg01686.html I can confirm the problem. I cannot build gcc 4.1.1-r1 with 4.1.1 (I probably built it fine with some previous version, not sure though). Direct link to gcc bugzilla discussing similar/same thing: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22313 After switching from CFLAGS="-march=k6-3 -mmmx -m3dnow -O2 -pipe -fomit-frame-pointer -g" to CFLAGS="-O1 -pipe " it builds w/o problem. As I understand comments on gcc site -g is the option that causes problem, ut I cannot verify it now... *** Bug 149236 has been marked as a duplicate of this bug. *** Created attachment 100188 [details, diff]
gcc41-pr22313.patch
i already merged this into our patchset ... guess i forgot to close the bug will be fixed in 4.1.1-r2 looks like this causes a regression with gfortran (Bug 155417) latest gcc-4.1 branch is OK so i'm gonna drop this patch from gcc-4.1.1 and just make people use gcc-4.1.2+ if they want this fixed *** Bug 161111 has been marked as a duplicate of this bug. *** |