From owner-freebsd-current@FreeBSD.ORG Tue Feb 28 21:34:17 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 6DCBE106566B; Tue, 28 Feb 2012 21:34:17 +0000 (UTC) Date: Tue, 28 Feb 2012 21:34:17 +0000 From: Alexander Best To: Dimitry Andric Message-ID: <20120228213417.GA86570@freebsd.org> References: <20120226213703.GA33988@freebsd.org> <4F4D34C8.9080507@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F4D34C8.9080507@FreeBSD.org> Cc: freebsd-toolchain@freebsd.org, freebsd-current@freebsd.org Subject: Re: setting CC/CXX/CPP unconditionally in src.conf X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 28 Feb 2012 21:34:17 -0000 On Tue Feb 28 12, Dimitry Andric wrote: > On 2012-02-26 22:37, Alexander Best wrote: > > any chance support for setting CC/CXX/CPP unconditionally in src.conf could be > > added before the release of freebsd 10.0? the way it is done atm is really not > > intuitive. the rule should really be: > > > > - make.conf = applies globally > > - src.conf = applies only to /usr/src > > ( maybe a ports.conf or port.conf could be introduced at some point, too) > > > > ... the current situation, where only certain variables can be set in src.conf > > is not ideal. > > I just committed r232263 to head, which should allow setting CC/CXX/CPP > in src.conf. Please try it out. it seems the latest libarchive import broke world with clang and without NO_WERROR=. i'm now trying with NO_WERROR= set. cheers. alex