From owner-freebsd-questions@freebsd.org Sat Oct 7 02:58:47 2017 Return-Path: Delivered-To: freebsd-questions@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 BAC4EE2AE70; Sat, 7 Oct 2017 02:58:47 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9A7ED7E944; Sat, 7 Oct 2017 02:58:47 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id 3B7965A9F12; Sat, 7 Oct 2017 02:58:40 +0000 (UTC) Date: Sat, 7 Oct 2017 02:58:40 +0000 From: Brooks Davis To: freebsd-questions@freebsd.org, freebsd-ports@freebsd.org Subject: Re: make ports use system clang & llvm Message-ID: <20171007025839.GA68389@spindle.one-eyed-alien.net> References: <20171006221058.GA98039@v007.zyxst.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="G4iJoqBmSsgzjUCe" Content-Disposition: inline In-Reply-To: <20171006221058.GA98039@v007.zyxst.net> User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Oct 2017 02:58:47 -0000 --G4iJoqBmSsgzjUCe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 06, 2017 at 11:10:58PM +0100, tech-lists wrote: > Hello, >=20 > Is there a way to make ports use system clang & llvm (now at v5) rather t= han=20 > pulling in llvm4? If so, please tell me what it is! Short verison: no. Longer version: Ports that depend on a specific LLVM version typically do so because they link to LLVM libraries. LLVM provides *no* API stability between releases so programs can only link to a narrow range of LLVM versions (1 version is common) and we can not ship the libraries with the base system because we would then be stuck with a single LLVM and clang version for the life of a STABLE branch (usually 5+ years). -- Brooks --G4iJoqBmSsgzjUCe Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJZ2ELfAAoJEKzQXbSebgfAhBQH/2ZKrtO3p930178J/MSfOK0l 6U9gXdqZ8lw0+DaW0dVM/Yhy0N3SEvoRwGv67qorF9jpilkXgAVhAnW1cVIAfSIo YrYFgXsQg8AM+WzhdajFyKe4O/lLH/brQvczXX2/8mAA/g9NTpcGGtStfsYJo7bI If24qdzusA0h4OKrIhlqV9jbGSvMPRsluA2Nmx8K3YS9pfnbkH/csOIbS4VQaru2 OASYelV2ZI+iiscHu0F/OKadSyeOgQqXkt0vKk/OL0FRPmp4WmI7CiwkKAPzpIzk StwuhDgZJmoa5Wqvvc36AXJ/Kej4yH95Wy/kYu4Wg0BSsNpFwwZuNny0SWPob2M= =NYYn -----END PGP SIGNATURE----- --G4iJoqBmSsgzjUCe--