Date: Mon, 19 May 2008 23:10:32 -0400 From: "Josh Carroll" <josh.carroll@gmail.com> To: "Dave Uhring" <duhring@charter.net> Cc: freebsd-stable@freebsd.org Subject: Re: Buildworld Fails RELENG_7 Message-ID: <8cb6106e0805192010n4bf6afb5hac521f81ebf16b63@mail.gmail.com> In-Reply-To: <20080520030118.GC1373@charter.net> References: <20080519165421.GA62264@charter.net> <20080519175358.GB55020@charter.net> <20080519180201.GI7468@bunrab.catwhisker.org> <20080519183614.GB55295@charter.net> <448wy6yviw.fsf@be-well.ilk.org> <20080519201408.GD79130@charter.net> <20080520000147.GA2824@lava.net> <20080520013825.GB1310@charter.net> <8cb6106e0805191908g2eb24babn4f4b3e532cc77f8e@mail.gmail.com> <20080520030118.GC1373@charter.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> No, even though it is a dual-core system. I did not want to chance a > race condition. I simply executed 'make buildworld' initially, then > 'make -DNO_CLEAN buildworld' when I encountered problems in the build. Ok, it was worth asking, just to rule out the obvious. I'm still not sure where your logic in using -DNOCLEAN comes in, for a failed build. I would expect that to continue to fail in most circumstances if it were already failing. So I think in one of your other mails you said you're installing something else now? Solaris? If so, this thread is moot, since you aren't running FreeBSD on the box anymore, and no one has been able to reproduce your problem. I think the most likely culprits have already been mentioned in the thread so far anyway. Josh
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8cb6106e0805192010n4bf6afb5hac521f81ebf16b63>