Well one can do that, yes, but by default any configure script is going to
look for g++ first, find an ancient g++4.2 installed in /usr/bin/g++ and
use that unless the user specifically sets CC. I'm a bit fuzzy on the
timeline of FreeBSD's transition to clang over the last few years and so
was
Some application software I use seems to prefer ancient gcc release or
gcc46 from ports rather than clang.
Is there a recommended autoconf recipe for third party software to use the
right compilers across FreeBSD versions?
- Murray
___
On Sep 12, 2013, at 7:32 PM, Murray Stokely wrote:
Some application software I use seems to prefer ancient gcc release or
gcc46 from ports rather than clang.
Is there a recommended autoconf recipe for third party software to use the
right compilers across FreeBSD versions?
I thought the
You might want to ask over in the ports... Since the ports system has a good
mechanism for specifying a good compiler to use.
I'm not sure that your approach will actually work, since it is a bit too
fuzzy, but I'm sure others who know better will fill this in...
Warner
On Sep 12, 2013, at
