From owner-freebsd-current@freebsd.org Mon Mar 6 06:52:53 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 4FFC3CFB30C; Mon, 6 Mar 2017 06:52:53 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 312E11189; Mon, 6 Mar 2017 06:52:52 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id v266sdtn020464; Sun, 5 Mar 2017 22:54:45 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: "FreeBSD CURRENT" , "FreeBSD ports" From: "Chris H" Subject: How many versions of clang/llvm are currently required to maintain a system Date: Sun, 05 Mar 2017 22:54:45 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit 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: Mon, 06 Mar 2017 06:52:53 -0000 I've finally been able to bootstrap CURRENT FreeBSD on some new hardware I picked up -- that is, successfully get world/kernel built/installed on it. I see there's a newer version of clang in base (4), which I had hoped that ports would pick up on, and use. But I suppose it's a bit early for ports to start requiring 4. That said; given the time it takes to build install fresh version(s) of these. Is there any way to limit the version /chosen/ by the ports tree/framework? It's painful firing up a build of a meta-port, and watch more than one version of clang/llvm be built for the BUILD_DEPENDS, only to have it cleaned and never installed, only to be built again, and again... You get the picture. :-) Anyway, as I indicated; I'm hoping to limit the ports framework to building/using only /one/ version; say >=3.9? I'd simply look through the system I have, but it's in a build session, that looks like it won't be finished for more than an hour. Thank you for all your time, and consideration. --Chris