[ANNOUNCE]: clang compiling ports

Matthias Andree mandree at FreeBSD.org
Tue Jun 21 10:58:46 UTC 2011

Am 21.06.2011 12:43, schrieb Baptiste Daroussin:

> Just be aware that stable clang has some issue with the stable binutils,
> to fix this make sure to use binutils from ports.
> To be able to test on stable:
> export CC=clang
> export CXX=clang++
> PATH=/usr/local/bin:${PATH} make -C myport
> the ld from localbase is found first so clang uses it.
> currently from my testing everything that succeed compiling with this
> also succeed on current
> and everything that fail on current also fails this way.

Thanks, however, this misses one particular error case, namely,
hardwired compiler names such as cc, c89, c99, gcc -- because these
remain in PATH. Possibly we can just create a dummy directory and stuff
all gcc-related tool names as hard links to [/usr]/bin/false in there
and stuff that early in the path, too, so you see if a port uses gcc.
For instance, the security/openvpn plugins did that.

More information about the freebsd-ports mailing list