Bug 198877

Summary: CPUTYPE in make.conf gets changed, breaks lang/gcc
Product: Base System Reporter: Johannes M Dieterich <jmd>
Component: miscAssignee: freebsd-ports-bugs (Nobody) <ports-bugs>
Status: Closed Overcome By Events    
Severity: Affects Some People Flags: gerald: maintainer-feedback-
Priority: ---    
Version: CURRENT   
Hardware: amd64   
OS: Any   
Attachments:
Description Flags
Patch adding GitHub/PyPI site handlers none

Description Johannes M Dieterich freebsd_committer freebsd_triage 2015-03-24 18:20:43 UTC 
ON CURRENT, if CPUTYPE?=core-avx2 is set in /etc/make.conf, the build system will automatically translate it to "-march=haswell". While this is correct and understood by clang, it breaks lang/gcc in the configure step (since the latest update to lang/gcc) :

configure:3587: /usr/ports/lang/gcc/work/build/./gcc/xgcc -B/usr/ports/lang/gcc/
work/build/./gcc/ -B/usr/local/x86_64-portbld-freebsd11.0/bin/ -B/usr/local/x86_
64-portbld-freebsd11.0/lib/ -isystem /usr/local/x86_64-portbld-freebsd11.0/inclu
de -isystem /usr/local/x86_64-portbld-freebsd11.0/sys-include    -c -g -O2 -pipe
 -march=haswell  -DLIBICONV_PLUG -fno-strict-aliasing  conftest.c >&5
conftest.c:1:0: error: bad value (haswell) for -march= switch
 /* confdefs.h */
 ^
configure:3591: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "GNU C Runtime Library"
| #define PACKAGE_TARNAME "libgcc"
| #define PACKAGE_VERSION "1.0"
| #define PACKAGE_STRING "GNU C Runtime Library 1.0"
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL "http://www.gnu.org/software/libgcc/"
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:3605: error: in `/usr/ports/lang/gcc/work/build/x86_64-portbld-freebsd
11.0/libgcc':
configure:3608: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.

I can reproduce the issue with CPUTYPE?=core-avx-i, which gets translated to -march=ivybridge.
Comment 1 Gerald Pfeifer freebsd_committer freebsd_triage 2015-03-24 21:30:24 UTC 
I don't think it's GCC's fault if "something" feeds it invalid input.

Who has / feels ownership of this piece of make.conf?
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2015-03-25 01:53:27 UTC 
The bug appears to be in the base system (/etc/make.conf).
Comment 3 Johannes M Dieterich freebsd_committer freebsd_triage 2015-03-25 14:41:38 UTC 
The same behavior can also be observed for devel/valgrind and (I suspect) for a lot of ports relying on gcc in their configure stage and not stripping -march= completely.
Comment 4 Johannes M Dieterich freebsd_committer freebsd_triage 2015-04-13 22:39:41 UTC 
It seems this is caused by changes introduced in r280159 to share/mk/bsd.cpu.mk

In this revision some CPUTYPES are changed (in particular, the haswell and ivybridge ones I have problems with). Now the pending update of lang/gcc to gcc4.9 will likely solve this issue as the aliases are then the same as for recent clangs again. Still, it is somewhat unsatisfying.
Comment 5 Kubilay Kocak freebsd_committer freebsd_triage 2015-10-24 09:33:56 UTC 
Created attachment 162410 [details]
Patch adding GitHub/PyPI site handlers
Comment 6 Kubilay Kocak freebsd_committer freebsd_triage 2015-10-24 09:34:20 UTC 
Comment on attachment 162410 [details]
Patch adding GitHub/PyPI site handlers

Ugh, ignore that.
Comment 7 Johannes M Dieterich freebsd_committer freebsd_triage 2016-03-20 04:06:13 UTC 
Not a problem any longer as with the later llvm/clang imports to HEAD more modern CPUTYPEs are supported.