Date: Sun, 31 Aug 1997 22:04:27 -0700 (PDT) From: "Jamil J. Weatherbee" <jamil@counterintelligence.ml.org> To: dkelly@hiwaay.net Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Buildworld failing (this happened yesterday also after cvsup to RELENG_22) Message-ID: <Pine.BSF.3.96.970831220313.811B-100000@counterintelligence.ml.org> In-Reply-To: <199709010405.XAA02641@nospam.hiwaay.net>
next in thread | previous in thread | raw e-mail | index | archive | help
What is the deal? I am not a cvsup expert by any means --- but isn't cvsup supposed to produce a perfect copy of the archive on the remote machine in an efficient and non-bandwidth intensive fashion? On Sun, 31 Aug 1997 dkelly@hiwaay.net wrote: > > > > Do you know how long that is going to take with a 160mb source tree over a > > 28.8 ---- I've done it before, not fun. > > > > On Mon, 1 Sep 1997 andrew@ugh.net.au wrote: > > > > > On Sun, 31 Aug 1997, Jamil J. Weatherbee wrote: > > > > > > > So why is it failing if the files are there, are those directories somehow > > > > not getting scanned for includes? > > > > > > Just a possibly wrong suggestion...try blowing away /usr/obj and /usr/src > > > and resupping (no idea why it would help...it seems like magic to me). > > I was having a different "make world" problem yesterday. Built a new > /usr/src > out of CTM's I had laying around then brought that up to date with cvsup. > Am thinking about trying it again with my old src tree. It's cvsup'ing right > now. Talking about RELENG_2_2. > > Have learned to prefer "cvsup -g" as sometimes cvsup gets confused and core > dumps. When it does it in an Xterm, I know where. Then delete the problem > files or directory, and re-run cvsup. > > Might not be such a bad idea to delete your problem source directory and > re-cvsup it back into shape. > > -- > David Kelly N4HHE, dkelly@hiwaay.net > ===================================================================== > The human mind ordinarily operates at only ten percent of its > capacity -- the rest is overhead for the operating system. > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970831220313.811B-100000>