Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 25 Sep 2014 14:50:18 -0400
From:      John Baldwin <jhb@freebsd.org>
To:        Marcel Moolenaar <marcel@xcllnt.net>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Poor state of the build infrastructure.
Message-ID:  <201409251450.18627.jhb@freebsd.org>
In-Reply-To: <FC0F5230-DF74-4740-A0A6-C2FDF022D094@xcllnt.net>
References:  <4496BEA3-9F6C-4F09-B8F6-68D97A331A60@xcllnt.net> <1643827.epFl9jnZN1@ralph.baldwin.cx> <FC0F5230-DF74-4740-A0A6-C2FDF022D094@xcllnt.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, September 24, 2014 7:33:46 pm Marcel Moolenaar wrote:
> 
> On Sep 24, 2014, at 12:54 PM, John Baldwin <jhb@freebsd.org> 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201409251450.18627.jhb>