From owner-freebsd-current@freebsd.org Fri Apr 7 00:35:45 2017 Return-Path: Delivered-To: freebsd-current@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 97CFDD3067A for ; Fri, 7 Apr 2017 00:35:45 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5D5C2D17; Fri, 7 Apr 2017 00:35:45 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.127] (helo=rmmprod05.runbox) by mailtransmit02.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1cwHsF-0008Nf-D2; Fri, 07 Apr 2017 02:35:35 +0200 Received: from mail by rmmprod05.runbox with local (Exim 4.86_2) (envelope-from ) id 1cwHsF-0001eu-B0; Fri, 07 Apr 2017 02:35:35 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); Fri, 07 Apr 2017 00:35:35 GMT From: "Jeffrey Bouquet" Reply-To: jbtakk@iherebuywisely.com To: "Brooks Davis" CC: "Russell L. Carter" , "freebsd-current" Subject: Re: how to mark llvm* forbidden? Date: Thu, 06 Apr 2017 17:35:35 -0700 (PDT) X-Mailer: RMM6 In-Reply-To: <20170406172618.GB62417@spindle.one-eyed-alien.net> Message-Id: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Apr 2017 00:35:45 -0000 On Thu, 6 Apr 2017 17:26:18 +0000, Brooks Davis wrote: > On Wed, Apr 05, 2017 at 06:18:37PM -0700, Russell L. Carter wrote: > > On 04/05/17 15:32, Chris H wrote: > > > On Wed, 5 Apr 2017 21:51:40 +0000 Brooks Davis w= rote > > >=20 > > >> On Wed, Apr 05, 2017 at 11:42:16AM -0700, Chris H wrote: > > >>> OK I'm chasing -CURRENT, and I performed an initial > > >>> install, followed by a new world/kernel && ports about a > > >>> mos ago. Last Friday, I svn upped the system (src && ports), > > >>> rebuilt/installed world/kernel. I just began rebuilding > > >>> the ports, only to find that when finished, I will likely > > >>> end up with every version of llvm && clang from version 3 > > >>> to the now current 4. My build session is currently tying > > >>> nearly every core on the CPU with llvm builds. Given that > > >>> llvm4 comes in base. Is there *any* reason I can not insist > > >>> that the ports I upgrade, or build, just use the version(s) > > >>> of clang/llvm in base? If so. How do I inform the ports > > >>> that they may *only* use the version(s) in base? > > >> > > >> In general you can't. There are many reasons including: the base ll= vm > > >> doesn't include the requisite cmake bits for cmake based ports, some > > >> ports use unstable APIs and require specific LLVM versions, and some= use > > >> LLVM tools or libraries that aren't built/installed as part of the b= ase > > >> system. > > >> > > >> There are probably some ports where the base clang is fine but that's > > >> probably mostly down to someone getting USES variables right. > > >> > > >> -- Brooks > > > Grumble.. That's what I was afraid I might hear. > > >=20 > > > Thanks, Brooks! Even if it's not what I was hoping to hear. :) > >=20 > > FWIW, this is biting me hard right now too. I feel your > > pain... I'm a c++17 junky but I might have to let go of > > llvm-devel. >=20 > If you want to track clang development, I would generally dis-recommend > the llvm-devel port. If you check out from upstream svn/git and build > with cmake and ninja, then you get pretty efficient incremental builds. > One nice think about the llvm build infrastructure is that you can use > it in place in the build's bin directory so you don't even need to > maintain an installed copy. >=20 > -- Brooks Can/should this be in /usr/ports/UPDATING?=20=