From owner-freebsd-current@freebsd.org Thu Apr 6 01:27:11 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 8EFC2D314C8 for ; Thu, 6 Apr 2017 01:27:11 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: from h2.pinyon.org (h2.pinyon.org [65.101.20.170]) (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 68D539D1 for ; Thu, 6 Apr 2017 01:27:11 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: by h2.pinyon.org (Postfix, from userid 58) id B183A1AC3A; Wed, 5 Apr 2017 18:18:39 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pinyon.org; s=DKIM; t=1491441519; bh=Cn5/j8Hq179J2kaepLSEomh2Syfkrt6tintMXL9hzP4=; h=Subject:To:References:From:Date:In-Reply-To; b=Y41o/N3chnv4vGwXqihJ1SzzklbZvD64inw8QOdHnJaQ/2CpiaU/Q6iMdnXef7KWJ oWMgFyJ6YlCivLixwmDgZM5XAPHwo0YbNAVDvB2Ixpop4rZQkzZGVmt+68xMyJ+mf4 c4a9u+REOq+VS0ru3JmS6qnKeZpLfE5q6m5WTdAI= X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on h2.n1.pinyon.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.1 Received: from [10.0.10.15] (h1.pinyon.org [65.101.20.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by h2.pinyon.org (Postfix) with ESMTPSA id A925D1AC26 for ; Wed, 5 Apr 2017 18:18:38 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pinyon.org; s=DKIM; t=1491441518; bh=Cn5/j8Hq179J2kaepLSEomh2Syfkrt6tintMXL9hzP4=; h=Subject:To:References:From:Date:In-Reply-To; b=kOxzsLtnP7OKWmAc35N/PPkpiUxXo30ZQ93nHuZdHgy5ZYYCtc1QpSFH+hLK/kav/ LcF+vIAtMBW1jNFtwk6p3NWtgE3ua5GXIy4v2aG2gy6JS9hL/UGyjeqyPt816rQHXi ClDkMPWqxsLp7DJftAH2NqJG2ac0LzGnOW74XBww= Subject: Re: how to mark llvm* forbidden? To: freebsd-current@freebsd.org References: <67e1da1eb0ff0550aab07f56d1f022ab@ultimatedns.net> <20170405215139.GA62417@spindle.one-eyed-alien.net> <26b7ef04eae1f095c399fae53eaaba39@ultimatedns.net> From: "Russell L. Carter" Message-ID: Date: Wed, 5 Apr 2017 18:18:37 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 In-Reply-To: <26b7ef04eae1f095c399fae53eaaba39@ultimatedns.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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: Thu, 06 Apr 2017 01:27:11 -0000 On 04/05/17 15:32, Chris H wrote: > On Wed, 5 Apr 2017 21:51:40 +0000 Brooks Davis wrote > >> 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 llvm >> 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 base >> 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. > > Thanks, Brooks! Even if it's not what I was hoping to hear. :) 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. Russell > --Chris > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >