Re: buildworld problems with today's sources

2002-07-01 Thread Peter Schultz
On Mon, 2002-07-01 at 09:02, Luigi Rizzo wrote: > On Mon, Jul 01, 2002 at 09:58:04AM -0400, Andrew Gallatin wrote: > ... > > That's actually rather scary. It implies that a freshly checked out > > tree checked out with plain 'cvs co src' is no longer buildable. > > c'mon... it is not that terrib

Re: buildworld problems with today's sources

2002-07-01 Thread Luigi Rizzo
On Mon, Jul 01, 2002 at 09:58:04AM -0400, Andrew Gallatin wrote: ... > That's actually rather scary. It implies that a freshly checked out > tree checked out with plain 'cvs co src' is no longer buildable. c'mon... it is not that terrible, just a matter of adding a -P flag luigi To Uns

Re: buildworld problems with today's sources

2002-07-01 Thread Andrew Gallatin
Luigi Rizzo writes: > On Mon, Jul 01, 2002 at 09:47:26AM -0400, Andrew Gallatin wrote: > > > > The same thing happened to me when buildworlding on a ~june 20th > > current box. > > Ruslan explained me the source of the problem... cvs does not > prune empty directories unless you specify

Re: buildworld problems with today's sources

2002-07-01 Thread Luigi Rizzo
On Mon, Jul 01, 2002 at 09:47:26AM -0400, Andrew Gallatin wrote: > > The same thing happened to me when buildworlding on a ~june 20th > current box. Ruslan explained me the source of the problem... cvs does not prune empty directories unless you specify a revision or a date. In my case i wanted

Re: buildworld problems with today's sources

2002-07-01 Thread Andrew Gallatin
The same thing happened to me when buildworlding on a ~june 20th current box. I removed CPUTYPE from /etc/make.conf, and I fsck'ed the disk in question (after a crash resulting from the condvar problem discussed here). And I removed -j4 from my make flags. One of these things (sorry that I don