Date: Mon, 19 May 2008 18:00:39 +0100 From: Doug Rabson <dfr@rabson.org> To: Dave Uhring <duhring@charter.net> Cc: Jeremy Chadwick <koitsu@FreeBSD.org>, freebsd-stable@freebsd.org Subject: Re: Buildworld Fails RELENG_7 Message-ID: <7AA1551A-D04D-4817-8028-E9CB6A87C0EA@rabson.org> In-Reply-To: <20080519165807.GB62264@charter.net> References: <20080519151739.GA50653@charter.net> <4AB77C7C-55F7-4CC3-B842-E684F6C899E3@rabson.org> <20080519163825.GA32372@charter.net> <20080519164221.GA76691@eos.sc1.parodius.com> <20080519165807.GB62264@charter.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19 May 2008, at 17:58, Dave Uhring wrote: > On Mon, May 19, 2008 at 09:42:21AM -0700, Jeremy Chadwick wrote: >> >> Is there some reason you're using -DNO_CLEAN, and haven't just nuked >> /usr/obj/* and done buildworld normally? I can't reproduce any of >> this >> behaviour on any of our RELENG_7 systems. > > I have repeately nuked /usr/obj. That is not going to put updated > header files > where they need to be. > > I'm using -DNO_CLEAN in order to get the system to a point where a > build just > might succeed without -DNO_CLEAN and I'm not getting there without > some header > files being in the right place. > > Remember I'm starting from a RELEASE userland. This is just about > as bad as > jumping from one full release to the next :( The thing is that a working buildworld doesn't depend on headers from / usr/include. One of the first thing it does is install a set of new headers in somewhere like /usr/obj/usr/src/tmp. At this point, it might be useful to see a log of a failed buildworld attempt to see what is going wrong.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7AA1551A-D04D-4817-8028-E9CB6A87C0EA>