Date: Tue, 25 Feb 2014 18:04:21 -0600 From: Brooks Davis <brooks@freebsd.org> To: Chris H <bsd-lists@bsdforge.com> Cc: freebsd-hackers <hackers@freebsd.org>, freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: How to prevent use of clang && llvm? Message-ID: <20140226000421.GA80747@lor.one-eyed-alien.net> In-Reply-To: <47ae4e8ed445c7e6fc46796d46b9a928.authenticated@ultimatedns.net> References: <47ae4e8ed445c7e6fc46796d46b9a928.authenticated@ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Feb 25, 2014 at 03:31:56PM -0800, Chris H wrote: > Greetings, > I'm in the process of performing an upgrade, and ran a preliminary check > to see what would be performed. During the process I encountered a > dialog(1) for both clang, and llvm3. It was for textproc/clucene. Which > wants devel/boost-libs, which depends on devel/boost-jam. I didn't require > clang, or llvm3 with the initial install of textproc/clucene (that I can see/recall). > But am presented with the dialog this time. I have WITHOUT_CLANG=true > in /etc/src.conf. Do I need to also add it to /etc/make.conf? Anything else? It looks like this is because boots requires a C++11 compiler and the default C++11 compiler is clang. From reading the source I deduce that FAVORITE_COMPILER=gcc in your make.conf may achieve the effect you require. -- Brooks --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iKYEARECAGYFAlMNL4RfFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl bnBncC5maWZ0aGhvcnNlbWFuLm5ldDY1NUQ1MTlDMjZBNzgyRTcyNTI5OUJGMDVE OEU4QkU5RjIzODFBRDQACgkQXY6L6fI4GtQ64gCgis5V/JlVAGwPHLcWtc4M1Zak 2QcAoI97y70X6jpJPErTKRedURL56fIC =oQUp -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140226000421.GA80747>