Date: Tue, 21 Jun 2011 12:58:45 +0200 From: Matthias Andree <mandree@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: [ANNOUNCE]: clang compiling ports Message-ID: <4E007965.20405@FreeBSD.org> In-Reply-To: <ab31cbf6a38344db10b0d48f9aa40869@etoilebsd.net> References: "<20110620153753.GA41541@freebsd.org>" <4E006F43.5010505@FreeBSD.org> <4E0070FB.1090607@FreeBSD.org> <4E007284.1060304@FreeBSD.org> <4E0074D6.4040308@FreeBSD.org> <ab31cbf6a38344db10b0d48f9aa40869@etoilebsd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E007965.20405>