Summary: | CPUTYPE in make.conf gets changed, breaks lang/gcc | ||||||
---|---|---|---|---|---|---|---|
Product: | Base System | Reporter: | Johannes M Dieterich <jmd> | ||||
Component: | misc | Assignee: | 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
Johannes M Dieterich
2015-03-24 18:20:43 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? The bug appears to be in the base system (/etc/make.conf). 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. 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. Created attachment 162410 [details]
Patch adding GitHub/PyPI site handlers
Comment on attachment 162410 [details]
Patch adding GitHub/PyPI site handlers
Ugh, ignore that.
Not a problem any longer as with the later llvm/clang imports to HEAD more modern CPUTYPEs are supported. |