Date: Tue, 26 Oct 2004 01:18:49 -0700 From: "David O'Brien" <obrien@freebsd.org> To: brian@aljex.com Cc: freebsd-current@freebsd.org Subject: Re: can't buildworld - boot2 Message-ID: <20041026081849.GB88522@dragon.nuxi.com> In-Reply-To: <1098763854.417dce4e8d52f@corpmail.siteone.net> References: <1098733044.417d55f46cc15@corpmail.siteone.net> <10185.128.101.36.205.1098738081.squirrel@128.101.36.205> <1098742333.417d7a3d920cf@corpmail.siteone.net> <1098763854.417dce4e8d52f@corpmail.siteone.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 26, 2004 at 12:10:54AM -0400, brian@aljex.com wrote: > possible clue: you mentioned -j > I had tried a -j4 , which was the first time I ever tried -j anything btw, > previously and it failed, but it didn't fail anywhere near the spot I showed. > After it failed I shrugged and thought "not surprising" and did a make clean > and make buildworld and got the failure in boot2 I originally posted If you need to get things "sane", I suggest 'rm -rf /usr/obj/*' followed by 'cd /usr/src ; make cleandir'. Or skip the rm -rf stage and do 'cd /usr/src ; make cleandir ; make cleandir'. > Either the initial failure screwed up the instance of bash and all I needed to > do was log out & in, or the use of bash vs csh is no good, or some change was > committed in the last few hours that fixed it, or -O2 -fno-strict-aliasing > works where -O doesn't. 'boot2' is built with -Os, so it overrides other settings. -- -- David (obrien@FreeBSD.org)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041026081849.GB88522>