Date: Mon, 21 Apr 2014 18:20:55 +0200 From: Mathieu Arnold <mat@FreeBSD.org> To: Matthieu Volat <mazhe@alkumuna.eu>, Mathieu Arnold <mat@FreeBSD.org> Cc: ports@freebsd.org, Robert Huff <roberthuff@rcn.com> Subject: Re: replacing gcc with clang Message-ID: <8540AA52D119E65F176AD5BE@ogg.in.absolight.net> In-Reply-To: <20140421175645.4730e3bc@freedom.alkumuna.eu> References: <535461FF.4090406@rcn.com> <2F29AD98517F1485E032775E@atuin.in.mat.cc> <20140421175645.4730e3bc@freedom.alkumuna.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
+--On 21 avril 2014 17:56:45 +0200 Matthieu Volat <mazhe@alkumuna.eu> wrote: | On Mon, 21 Apr 2014 11:58:58 +0200 | Mathieu Arnold <mat@FreeBSD.org> wrote: | |> +--On 20 avril 2014 20:10:39 -0400 Robert Huff <roberthuff@rcn.com> |> wrote: |> | Is there a authoritative list of those ports know to not build with |> | clang 3.2/3.4? |> |> No, but you can grep for USE_GCC in the ports tree to find that out. |> |> -- |> Mathieu Arnold | | That is a start, but you would raise many false positives with ports | building and working fine with clang, but that have an "GCC" option to | use things like openmp, profiled builds, etc. Hum, ports that USE_GCC for openmp are doing it wrong, they should be doing USES=compiler:openmp :-) There's bound to be some false positives, yes, but not much so it would be a nice start. -- Mathieu Arnold
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8540AA52D119E65F176AD5BE>