From owner-freebsd-current@FreeBSD.ORG Thu Sep 25 19:55:17 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9D79D7A2 for ; Thu, 25 Sep 2014 19:55:17 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 748067FB for ; Thu, 25 Sep 2014 19:55:17 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id ECA5AB97C; Thu, 25 Sep 2014 15:55:15 -0400 (EDT) From: John Baldwin To: Marcel Moolenaar Subject: Re: Poor state of the build infrastructure. Date: Thu, 25 Sep 2014 14:50:18 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <4496BEA3-9F6C-4F09-B8F6-68D97A331A60@xcllnt.net> <1643827.epFl9jnZN1@ralph.baldwin.cx> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201409251450.18627.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 25 Sep 2014 15:55:16 -0400 (EDT) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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, 25 Sep 2014 19:55:17 -0000 On Wednesday, September 24, 2014 7:33:46 pm Marcel Moolenaar wrote: > > On Sep 24, 2014, at 12:54 PM, John Baldwin wrote: > > > On Tuesday, September 23, 2014 09:29:48 AM Marcel Moolenaar wrote: > >> What is going on here? > >> Are we still in some kind of flux and people aren't done yet or is > >> this the intended state by virtue of noone having anything left on > >> there TODO list? > > > > Sorry to ask a dumb question, but are you sure you did the make buildworld > > first? Shouldn't that have errored if it couldn't build crt1? > > The root cause problem was that MAKEOBJDIRPREFIX was not set > to whatever it was set to during buildworld. That was easy > enough to figure out when a bunch of things don't add up. Ok. > But neither problem mentioned in the email had anything to > do with MAKEOBJDIRPREFIX. Having to set the COMPILER_TYPE > as part of an install is a bug. Entering a powerpc buildenv > and having a compiler that builds for the host (or maybe > just some default) is a regression. Agreed on COMPILER_TYPE, but I think the path thing has always been true in make buildenv because we don't build cross-tools for things like 'cp'. -- John Baldwin