From owner-svn-ports-all@freebsd.org Wed Dec 27 16:13:17 2017 Return-Path: Delivered-To: svn-ports-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D1B2E9EC2E; Wed, 27 Dec 2017 16:13:17 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E138F6B95E; Wed, 27 Dec 2017 16:13:16 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id 202E41558F; Wed, 27 Dec 2017 16:13:16 +0000 (UTC) Date: Wed, 27 Dec 2017 16:13:16 +0000 From: Alexey Dokuchaev To: Jan Beich 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: <20171227161316.GA59585@FreeBSD.org> References: <201712271041.vBRAfUnn041527@repo.freebsd.org> <20171227104922.GA83619@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2017 16:13:17 -0000 On Wed, Dec 27, 2017 at 01:47:35PM +0100, Jan Beich wrote: > Alexey Dokuchaev 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: I was mostly concerned because LLVM ports take quite some time to build and package, so I always worry when this requirement bumps. Providing a little technical background behind changes occurring in important and heavy infrastructure port(s) would help stupid people like myself to understand the current state of affairs and direction better. > - 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. Thank you, that was quite helpful, I appreciate the taken time to write these things up. ./danfe