Date: Tue, 24 Jan 2017 15:37:40 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: jbtakk@iherebuywisely.com Cc: current <current@freebsd.org> Subject: Re: command line environment and port to equal CURRENT clang? Message-ID: <3DC82C84-DCD3-4278-BCE6-FF7E0087B23F@FreeBSD.org> In-Reply-To: <E1cVpVV-0000Z4-EV@rmm6prod02.runbox.com> References: <E1cVpVV-0000Z4-EV@rmm6prod02.runbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_30153947-07FA-4AE4-9024-94DBEF5F8A51 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 24 Jan 2017, at 02:02, Jeffrey Bouquet <jbtakk@iherebuywisely.com> = wrote: >=20 > On Mon, 23 Jan 2017 20:18:18 +0100, Dimitry Andric <dim@FreeBSD.org> = wrote: >=20 >> On 23 Jan 2017, at 05:32, Jeffrey Bouquet <jbtakk@iherebuywisely.com> = wrote: >>>=20 >>> ... that may work in /usr/src/sbin for example? >>> make clang=3D[/usr/ports/lang/??]clang-foo clang+ depend; make; = # so that a buildworld is not needed? >>> or that would have to be created as a feature.. >>=20 >> The following appears to work: >>=20 >> pkg install llvm39 >> export CC=3D/usr/local/bin/clang39 >> export CXX=3D/usr/local/bin/clang++39 >> export CPP=3D/usr/local/bin/clang-cpp >> cd /usr/src/sbin >> make obj >> make depend >> make >>=20 >> Note that this may pick up the wrong versions of libraries, so do not >> be amazed if stuff blows up. >>=20 >> Also note that clang in base has a few patches which might not be in = the >> port, so you could also run into unexpected bugs in the port. >>=20 >> -Dimitry >=20 > Works! on 9 out of ten binaries at least. [1] Even so good from here = that someone > may wish to put it in /usr/src/UPDATING but with an additional = reference to how > to find the most likely llvm since that may change over time... Which would be very unwise, and lead to many problem reports, since buildworld is carefully building things in the right order, making sure the headers and libraries are of the matching versions for the binaries. E.g., people should only use this method if they know exactly what they are doing, and how it can blow up in various interesting ways. -Dimitry --Apple-Mail=_30153947-07FA-4AE4-9024-94DBEF5F8A51 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.30 iEYEARECAAYFAliHZr8ACgkQsF6jCi4glqMquQCgkSpfFSe6qZ4ZGFeGRMlJC7hP lAYAn1kElMXXNqQ4Kdyp7O4zFfpd3aSu =kbrn -----END PGP SIGNATURE----- --Apple-Mail=_30153947-07FA-4AE4-9024-94DBEF5F8A51--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DC82C84-DCD3-4278-BCE6-FF7E0087B23F>