Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 4 Nov 2000 13:06:19 -0800
From:      "David O'Brien" <obrien@FreeBSD.ORG>
To:        =?iso-8859-1?Q?Joachim_Str=F6mbergson?= <watchman@ludd.luth.se>
Cc:        FreeBSD-Stable <freebsd-stable@FreeBSD.ORG>
Subject:   Re: Buildworld failure of STABLE as of 18:00 CET 2000-11-03
Message-ID:  <20001104130619.A23663@dragon.nuxi.com>
In-Reply-To: <3A040090.D80A4AAC@ludd.luth.se>; from watchman@ludd.luth.se on Sat, Nov 04, 2000 at 01:26:56PM %2B0100
References:  <3A032D99.9345F708@ludd.luth.se> <3A0332EF.9E175525@urx.com> <3A040090.D80A4AAC@ludd.luth.se>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 04, 2000 at 01:26:56PM +0100, Joachim Strömbergson wrote:
> Kent Stewart wrote:
> > There have been some complaints about buildworlds failing with the -j
> > option specified. You might leave that off an try it again. I didn't
> > specify a -j parameter and it worked.
> 
> I reran the build without the -j flag. Crash and burn on the same spot.

The damaged done by the previsous -j run would still be there if you used
a -DNOCLEAN on your second build.  (I assume the build broke in the linux
module build).
 
> > Since I didn't even have a warning, I would suspect something in your
> > file system is corrupt. FWIW, I cvsup'ed at 1109 (1909 GMT) 3-Nov.
> I'm re-cvsupping right now. Hopefully that will fix it. Otherwise I need
> to really start to dig into my cvs and see what's up.

CVSup'ing wont fix your problem.  You need to clean our /usr/obj/

-- 
-- David  (obrien@FreeBSD.org)
          GNU is Not Unix / Linux Is Not UniX


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




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