Summary: | sys-devel/gcc-4.4.5 emerge fails with -march=native | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Clemente Aguiar <clemente.aguiar> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log zipped
build.log and environment for build with -mnoavx |
Description
Clemente Aguiar
2011-07-03 19:55:04 UTC
> internal compiler error: in dwarf2out_frame_debug_expr, at dwarf2out.c:2292
that indicates a problem with your gcc installation
As I mentioned it only fails with -march=native. Without -march=native an # emerge -e system builds totally, but with -march=native an # emerge -e system only gcc fails to build. What else can I say. Here's the same problem. I made a fresh install yesterday with build from 30-06-2011 and I have the same problem. -march=native gcc fails to compile -march=core2 gcc compiles without errors If I have enabled the USE-Flag "fortran" I got this error libtool: link: /usr/x86_64-pc-linux-gnu/bin/ranlib .libs/libgfortran.a libtool: link: ( cd ".libs" && rm -f "libgfortran.la" && ln -s "../libgfortran.la" "libgfortran.la" ) If I disable fortran (-fortran) I got the same errors like described above. Reproducable: Always Attach full build.log please (In reply to comment #4) > Attach full build.log please When trying to upload attachment got message that there is an 1000 KB limit. $ ll /var/tmp/portage/sys-devel/gcc-4.4.5/temp/build.log -rw-rw---- 1 portage portage 5186694 Jul 3 20:52 /var/tmp/portage/sys-devel/gcc-4.4.5/temp/build.log In the meantime I put the log in: http://paste.pocoo.org/show/435088/ If not adequate please suggest other solution. Created attachment 279607 [details]
build.log zipped
Searching is always fun. Use -mno-avx on 4.4. *** This bug has been marked as a duplicate of bug 357287 *** Created attachment 279909 [details]
build.log and environment for build with -mnoavx
As can be seen from the build.log and build environment that I attached, the error persists even with -mnoavx. "-mno-avx" not "-mnoavx". if it still fails after that change take it up on the other bug report. *** This bug has been marked as a duplicate of bug 357287 *** |