Date: Wed, 27 Dec 2017 13:47:35 +0100 From: Jan Beich <jbeich@FreeBSD.org> To: Alexey Dokuchaev <danfe@FreeBSD.org> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r457360 - head/Mk/Uses Message-ID: <h8sc-tk0o-wny@FreeBSD.org> In-Reply-To: <20171227104922.GA83619@FreeBSD.org> (Alexey Dokuchaev's message of "Wed, 27 Dec 2017 10:49:22 %2B0000") References: <201712271041.vBRAfUnn041527@repo.freebsd.org> <20171227104922.GA83619@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexey Dokuchaev <danfe@FreeBSD.org> writes: > On Wed, Dec 27, 2017 at 10:41:30AM +0000, Jan Beich wrote: > >> New Revision: 457360 >> URL: https://svnweb.freebsd.org/changeset/ports/457360 >> >> Log: >> Update USES=compiler:c++14-lang to Clang 5.0 on FreeBSD 10 > > What was the reason behind this change? Do we really need a reason to update? ;) Here's an incomplete list: - Many projects don't care about old compilers; Clang support is usually driven by OS X and ASan users - Clang 4.0 is no longer maintained upstream; unlike GCC maintenance cycles are very short (around half a year) - FreeBSD 11.2 (aka /stable/11) and FreeBSD 12.0 (aka /head) already use Clang 5.0 in base - devel/llvm50 can build more ports with -flto=thin -fuse-ld=lld - Better C++17 support but still incomplete due to old libc++ in base - Mesa switched to llvm50 in r457264 -> less build dependencies - www/firefox switched to llvm50 in r457267 -> less build dependencies > Why on FreeBSD 10, what about 11 and 12-CURRENT? USES=compiler:c++14-lang is nop for FreeBSD 11 or later because Clang is new enough to support C++14. To be removed after FreeBSD 10.* reaches EOL. Architectures stuck with GCC don't differentiate between C++11 and C++14 capable compiler.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?h8sc-tk0o-wny>