Summary: | dev-lang/gnat-gcc-4.2.3 fails to emerge | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Felipe Balbi <me> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | usr.gentoo |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
config.log |
Description
Felipe Balbi
2010-02-24 12:37:58 UTC
Please attach the entire config.log and build log and reopen this bug report. Created attachment 221097 [details]
build.log
The same happens with gnat-gcc-4.3.2
Created attachment 221099 [details]
config.log
also happens with 4.3.2
There you have it :-) sorry for the long delay. and here's the issue, gnatgcc doesn't understand core2 arch: configure:3197: /var/tmp/portage/dev-lang/gnat-gcc-4.3.2/work/usr/bin/gnatgcc -O2 -march=core2 -pipe -L/var/tmp/portage/dev-lang/gnat-gcc-4.3.2/work/usr/lib/gnatgcc/i686-pc-linux-gnu/4.1 conftest.c >&5 conftest.c:1: error: bad value (core2) for -march= switch conftest.c:1: error: bad value (core2) for -mtune= switch and because of that, it fails when trying to compile anything: configure:3239: error: C compiler cannot create executables (In reply to comment #5) > and here's the issue, gnatgcc doesn't understand core2 arch: > > configure:3197: /var/tmp/portage/dev-lang/gnat-gcc-4.3.2/work/usr/bin/gnatgcc > -O2 -march=core2 -pipe > -L/var/tmp/portage/dev-lang/gnat-gcc-4.3.2/work/usr/lib/gnatgcc/i686-pc-linux-gnu/4.1 > conftest.c >&5 > conftest.c:1: error: bad value (core2) for -march= switch > conftest.c:1: error: bad value (core2) for -mtune= switch > > and because of that, it fails when trying to compile anything: > > configure:3239: error: C compiler cannot create executables changing core2 to i686 works fine: CFLAGS="-O2 -march=i686 -pipe" emerge dev-lang/gnat-gcc So you shouldn't use invalid cflags for older compilers. *** Bug 316917 has been marked as a duplicate of this bug. *** |