Summary: | sys-devel/gcc-4.6.4 - Bootstrap comparison failure! | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pavel Shirov <passnet> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | b.brachaczek |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=539950 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
gcc-4.6.4 build.log.xz
gcc-build-logs.tar.bz2 |
Description
Pavel Shirov
2014-08-05 05:46:50 UTC
Please attach to this bug report the entire build log and any other files that the build log says should be attached when filing a bug report. Created attachment 382314 [details]
gcc-4.6.4 build.log.xz
Created attachment 382316 [details]
gcc-build-logs.tar.bz2
I was hit by the same problem. Using this configuration helped: $ grep gcc /etc/portage/package.env/x86_64-pc-linux-gnu sys-devel/gcc gcc.conf $ cat /etc/portage/env/gcc.conf CFLAGS="-O2 -pipe" CXXFLAGS="${CFLAGS}" LDFLAGS="-Wl,-O1 -Wl,--as-needed" Notice the lack of any -march= flag. (In reply to Bartosz Brachaczek from comment #4) > I was hit by the same problem. Using this configuration helped: > > $ grep gcc /etc/portage/package.env/x86_64-pc-linux-gnu > sys-devel/gcc gcc.conf > $ cat /etc/portage/env/gcc.conf > CFLAGS="-O2 -pipe" > CXXFLAGS="${CFLAGS}" > LDFLAGS="-Wl,-O1 -Wl,--as-needed" > > Notice the lack of any -march= flag. By "the same problem" do you mean specifially building 4.6.4 using 4.7.3? Note the `emerge --info` the reporter gives is using 4.7.3. (In reply to Anthony Basile from comment #5) > By "the same problem" do you mean specifially building 4.6.4 using 4.7.3? > Note the `emerge --info` the reporter gives is using 4.7.3. That was building 4.6.4 using some 4.8.x version, IIRC. I can try to reproduce and send you my system configuration if this could help. gcc-4.9 is stable now, so throwing away older bugs we don't plan on doing backports for as this should be fixed w/4.9+. please re-open if it's still an issue with 4.9.3+ though. |