Issue #2878 has been updated by arc...@b1t.name.
Can't remember correctly what was there. Probably Firefox redefined path so
/usr/local/bin/gcc was selected first before /usr/bin/gcc.
Bug #2878: [fix] CCVER problem when using clang and cpu extensions (in
Issue #2878 has been updated by dragonflybsd1.
i'll need to see an actual excerpt to understand what you mean. I don't know
what you mean by "shadow". lang/gcc simply being installed doesn't affect
anything.
Bug #2878: [fix] CCVER problem when using c
Issue #2878 has been updated by arc...@b1t.name.
Well, those ports are devel/clang* and www/firefox*. If lang/gcc is installed
it shadows /usr/bin/gcc and thus CCVER doesn't works.
Bug #2878: [fix] CCVER problem when using clang and cpu extensions (intri
Issue #2878 has been updated by marino.
"3. gcc/gxx can be superseded too as some ports just hardcode compiler names."
Any port that hardcodes "gcc" is wrong. that's considered a bug, even when GCC
is specified for the port. If you find a port like that, open a PR at FreeBSD.
---
Issue #2878 has been updated by arc...@b1t.name.
Subject changed from CCVER problem when using clang and cpu extensions
(intrinsics) to [fix] CCVER problem when using clang and cpu extensions
(intrinsics)
Looks like CCVER configuration for clang misses a few things:
1. INCOPT needs "-isystem /
