On 2017/09/28 15:06, Jeremie Courreges-Anglas wrote: > That would disable said ports on eg amd64, like what we have now > (NOT_FOR_ARCHS).
Yes. It's the way I've done it for some other things (e.g. festival) and I'd rather be consistent. > The first compiler that matches criteria will be chosen. On > clang-based architectures, even though gcc is still compiled in > base, ‘base-gcc’ never matches. > > I understand that relying on gcc-4.2.1 is not a long-term solution, but > I wonder why 'base-gcc' couldn't just set up a port to use > /usr/bin/g(cc|++). > > After all, we still need gcc-4.2.1 in base for things like > sysutils/firmware/vmm: > > # XXX errors with with clang > # ./src/string.c:24:16: error: invalid output constraint '=Qi' in asm > CC = /usr/bin/gcc I have a feeling newer gcc might be a simpler proposition than clang..
