Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Mar 2005 18:45:32 +0200
From:      Giorgos Keramidas <keramida@freebsd.org>
To:        Jeff Blank <jb000002@mr-happy.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: buildworld 17 Mar 2005 -CURRENT, top.local.h
Message-ID:  <20050321164532.GB3695@orion.daedalusnetworks.priv>
In-Reply-To: <20050321164008.GA39682@mr-happy.com>
References:  <20050318152717.GA64576@mr-happy.com> <20050320041724.GA20378@gothmog.gr> <20050321164008.GA39682@mr-happy.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2005-03-21 11:40, Jeff Blank <jb000002@mr-happy.com> wrote:
>On Sun, Mar 20, 2005 at 06:17:24AM +0200, Giorgos Keramidas wrote:
># On 2005-03-18 10:27, jb000002@mr-happy.com wrote:
># > I seem to get this error (or one very similar) about top.local.h every
># > second or third time I make buildworld.
># >
># > [...]
># > ===> usr.bin/top (all)
># > cc -O2 -fno-strict-aliasing -pipe  -DHAVE_GETOPT -DHAVE_STRERROR -I/usr/src/usr.bin/top -I/usr/src/usr.bin/top/../../contrib/top -I. -DORDER  -c /usr/src/usr.bin/top/../../contrib/top/commands.c
># > make: don't know how to make /usr/src/usr.bin/top/top.local.h. Stop
># > *** Error code 2
># It seems someone is looking for a file that isn't there (yet).
>
> make is looking for it in /usr/src/usr.bin/top, but the file is
> in fact being created (on-the-fly) in /usr/obj/usr/src/usr.bin/top.
>
># You're not using -j 4 or something similar, right?
>
> This one happened to be a parallel build (-j 2), but it's the first
> time I've done that.  All my other top.local.h problems have been with
> serial builds.  Of course, I can't recreate it with a serial build on
> -CURRENT now.  I'll keep an eye on it, but since I just have a P3-450,
> it could take some time.

If you do get this again with a parallel build and you get a chance to
do a serial build off the same source tree, make sure you start with a
clean /usr/obj and see if the serial build fails too.  If yes, it's
probably a bug that should be fixed.

Thanks for the followup :-)



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