Date: Sun, 24 Sep 2000 14:40:19 -0400 From: Bill Moran <wmoran@columbus.rr.com> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: FAQ's (was: Makeworld is dying...) Message-ID: <39CE4A93.CED4E287@columbus.rr.com> References: <39C42DF4.978A63C@urx.com> <Pine.LNX.4.10.10009170918240.13465-100000@shark.harmonic.co.il> <20000917160006.D67912@wantadilla.lemis.com> <20000918154418.P8111@moose.bri.hp.com> <20000924095410.A65590@wantadilla.lemis.com> <20000924092354.A473@freebee.attica.home> <20000924003413.A2018@Odin.AC.HMC.Edu> <20000924104652.A1327@freebee.attica.home> <20000924112423.A22965@Odin.AC.HMC.Edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Brooks Davis wrote: > I stand corrected with regards to the behavior of CVSup. I believe that > in general this failure to delete files will results in wasted space and > nothing more. I've certinalty never done this and haven't had problems > attributable to it. Also, the FreeBSD build process generally > seems to explicitly lists files rather then including them by wild cards > so extra files should have no effect. That said, I'll admit that most > of the tenish systems I update have been switched to CVSup a repository > and then check out their source from it so I can maintain local changes > which would midigate this problem if it were happening. Not to try to continue this discussion on after it's concluded, but I've seen this kind of problem with cvsup. I had a machine that had gone through some weird gyrations with regards to updating, and finally I decided to just cvsup to the latest and leave it at that. I cvsupped RELENG_4 several times (at lease three) because I couldn't get a make buildworld to finish successfully. In this case I wasn't aware of the fix recently posted here, so I simply trashed the entire /usr/src directory and did a new cvsup. That fixed it (built fine after that) Now, this doesn't give anyone very much to diagnose with, but apparently stale files in the cvs tree DO pose problems to the build process. If I ever manage to get this problem again, I'll do a snapshot of the source tree and see if I can figure out where things went wrong. Perhaps there are some ambiguities in the build process that can be corrected. -Bill 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?39CE4A93.CED4E287>