Date: Mon, 21 Apr 2014 17:56:45 +0200 From: Matthieu Volat <mazhe@alkumuna.eu> To: Mathieu Arnold <mat@FreeBSD.org> Cc: ports@freebsd.org, Robert Huff <roberthuff@rcn.com> Subject: Re: replacing gcc with clang Message-ID: <20140421175645.4730e3bc@freedom.alkumuna.eu> In-Reply-To: <2F29AD98517F1485E032775E@atuin.in.mat.cc> References: <535461FF.4090406@rcn.com> <2F29AD98517F1485E032775E@atuin.in.mat.cc>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/z_TWEBYuD4wGLn2dqK_2G/C Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable 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? >=20 > No, but you can grep for USE_GCC in the ports tree to find that out. >=20 > --=20 > Mathieu Arnold That is a start, but you would raise many false positives with ports buildi= ng and working fine with clang, but that have an "GCC" option to use things= like openmp, profiled builds, etc. --=20 Matthieu Volat <mazhe@alkumuna.eu> --Sig_/z_TWEBYuD4wGLn2dqK_2G/C Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iEYEARECAAYFAlNVP8QACgkQ+ENDeYKZi35HZwCeJb58GhqgKj9bMuELlitlRQ4y ViUAn2sg4dq2keeUgt7J/ACVaK7dsfLZ =g0bO -----END PGP SIGNATURE----- --Sig_/z_TWEBYuD4wGLn2dqK_2G/C--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140421175645.4730e3bc>