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
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
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 a
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
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 terrible,
I did the following (on a -STABLE system):
cvs co src
cd src
make MAKEOBJDIRPREFIX=`pwd`/../usr/obj buildworld
and got the error below.
Any ideas ? Am i doing something wrong ?
cheers
luigi
=== gnu/usr.bin/tar
rm -f tar addext.o argmatch.o backupfile.o
