Summary: | dev-lang/gnat-gcc-4.3.5 fails to compile in the config phase | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | robwobbol |
Component: | [OLD] Unspecified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | the ./configure log |
Description
robwobbol
2014-03-18 23:08:58 UTC
configure:3197: /var/tmp/portage/dev-lang/gnat-gcc-4.3.5/work/usr/bin/gnatgcc -march=corei7-avx -O2 -pipe -ggdb -L/var/tmp/portage/dev-lang/gnat-gcc-4.3.5/work/usr/lib conftest.c >&5 conftest.c:1: error: bad value (corei7-avx) for -march= switch This reveals that the -march=corei7-avx switch isn't understood; from a quick guess, I think gcc 4.3.5 might be too old and thus I suggest you set CFLAGS="-O2 -pipe -march=native", upgrade the compiler and then set it back as you see fit. Going on your hunch I attempted to emerge dev-lang/gnat-gcc: 3.4.6 4.1.2 4.2.3 4.3.5 4.3.6 4.4.3 4.4.5 4.4.7 4.5.4 4.6.4 (all of the avalible versions in the main tree) with the -march=corei7-avx flag. and receved the same error on all versions. I resolved to build with the native flag and leave it alone. As a side note:this ebuild seems to be downloading a precompiled gnat-gcc compiler. Why would it use that when I have a previous version installed? Another thought:Is it our duty to clean the input to this compiler or is it their duty to accept all valiad -march flags? |