Summary: | dev-lang/gnat-gcc-4.6.4 - conftest.c:1: error: bad value (corei7-avx) for -march= switch | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Nikolaos Chatzidakis <nikhatzi> |
Component: | [OLD] Development | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
config.log |
Description
Nikolaos Chatzidakis
2014-11-08 15:02:51 UTC
checking for C compiler default output file name... configure: error: in `/var/tmp/portage/dev-lang/gnat-gcc-4.6.4/work/build': configure: error: C compiler cannot create executables See `config.log' for more details. Please attach that config.log. Created attachment 388870 [details]
config.log
Here you are, hope it helps. Thank you for your time. :)
(In reply to Jeroen Roovers from comment #1) > checking for C compiler default output file name... > configure: error: in `/var/tmp/portage/dev-lang/gnat-gcc-4.6.4/work/build': > configure: error: C compiler cannot create executables > See `config.log' for more details. > > Please attach that config.log. Jeroen, in the config.log, i see this: conftest.c:1: error: bad value (corei7-avx) for -mtune= switch Maybe this is the issue? If it is, why is corei7-avx a bad value? I configure my flags using the gentoo wiki --> http://wiki.gentoo.org/wiki/Safe_CFLAGS#Core_i3.2Fi5.2Fi7_.26_Xeon_E3.2FE5.2FE7 Because the gcc version used to build gnat-gcc is a a little old and does not "know" about existence of modern processors. Drop any -march/mtune from ???FLAGS and it should work. (In reply to David Kredba from comment #4) > Because the gcc version used to build gnat-gcc is a a little old and does > not "know" about existence of modern processors. > Drop any -march/mtune from ???FLAGS and it should work. But, if i drop the march from my CFLAGS, won't there be a problem with portage? After all, that's why we have CFLAGS on gentoo... Isn't there any other workaround to emerge gnat-gcc? (In reply to Nikolaos Chatzidakis from comment #5) > (In reply to David Kredba from comment #4) > > Because the gcc version used to build gnat-gcc is a a little old and does > > not "know" about existence of modern processors. > > Drop any -march/mtune from ???FLAGS and it should work. > > But, if i drop the march from my CFLAGS, won't there be a problem with > portage? After all, that's why we have CFLAGS on gentoo... Isn't there any > other workaround to emerge gnat-gcc? Anyway, I removed my march from CFLAGS only to emerge gnat-gcc and it worked... I hope in the future this will be resolved. I meant temporarily, of course. IMO it will be solved only if a) ada will be accepted as main Gentoo supported language or b) gnat-gcc will be following trunk gcc more closely. I prefer variant a). Needed toolchain.eclass changes are very small for enabling Ada system wide, you only need working gnat-gcc once or Ada language included in Gentoo installation snapshots. (In reply to David Kredba from comment #7) > I meant temporarily, of course. > > IMO it will be solved only if > a) ada will be accepted as main Gentoo supported language > or > b) gnat-gcc will be following trunk gcc more closely. > > I prefer variant a). > > Needed toolchain.eclass changes are very small for enabling Ada system wide, > you only need working gnat-gcc once or Ada language included in Gentoo > installation snapshots. Thank you for the help, i hope in the future gnat-gcc won't have problems as such. :) |