Date: Fri, 24 Jul 2015 07:19:17 +0200 From: Matthieu Volat <mazhe@alkumuna.eu> To: Don Lewis <truckman@FreeBSD.org> Cc: stable@FreeBSD.org Subject: Re: MFC r282973 (disable libgomp build) and r283060 (disable libgcov build)? Message-ID: <20150724071917.6a1fd3a3@freedom> In-Reply-To: <201507202103.t6KL31mb092619@gw.catspoiler.org> References: <201507202103.t6KL31mb092619@gw.catspoiler.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/+pliA81zQ7ABpmLZj5QRJlz Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 20 Jul 2015 14:03:01 -0700 (PDT) Don Lewis <truckman@FreeBSD.org> wrote: > Should r282973 and r283060 be MFCed to FreeBSD 10? On amd64 and i386, > which use clang as their base compiler and don't have gcc in base by > default, the math/scilab port uses clang for cc and c++ compilation, but > finds /usr/include/omp.h (and links to libgomp from lang/gcc). The > build succeeds, but I suspect this may not run properly. Does it mean the door to an openmp-enabled cc in base is closed? I'm not fond of lang/gcc as openmp "provider": if a port use c++, it will c= ause linkage headaches with libc++ (I never was able to have graphics/darkt= able working, for example). --=20 Matthieu Volat <mazhe@alkumuna.eu> --Sig_/+pliA81zQ7ABpmLZj5QRJlz Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlWxytUACgkQ+ENDeYKZi36GTQCfYvweHOE4Cm8wHQm5ehrL0yVi LKIAnj0oVWewB9hA8CJID6ThCdVcDBzM =5oNK -----END PGP SIGNATURE----- --Sig_/+pliA81zQ7ABpmLZj5QRJlz--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150724071917.6a1fd3a3>