From owner-freebsd-current@freebsd.org  Wed Apr  5 18:41:07 2017
Return-Path: <owner-freebsd-current@freebsd.org>
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 758AFD30471
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Wed,  5 Apr 2017 18:41:07 +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 42F30E40
 for <freebsd-current@freebsd.org>; Wed,  5 Apr 2017 18:41:06 +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 v35IgATR048393
 for <freebsd-current@freebsd.org>; Wed, 5 Apr 2017 11:42:16 -0700 (PDT)
 (envelope-from bsd-lists@bsdforge.com)
To: "FreeBSD CURRENT" <freebsd-current@freebsd.org>
From: "Chris H" <bsd-lists@bsdforge.com>
Subject: how to mark llvm* forbidden?
Date: Wed, 05 Apr 2017 11:42:16 -0700
Content-Type: text/plain; charset=UTF-8; format=fixed
MIME-Version: 1.0
Message-id: <67e1da1eb0ff0550aab07f56d1f022ab@ultimatedns.net>
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
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Apr 2017 18:41:07 -0000

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?

Thank you for all your time, and consideration.

--Chris