From owner-freebsd-current@FreeBSD.ORG Sun Jul 13 08:39:34 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0DBE37B401 for ; Sun, 13 Jul 2003 08:39:34 -0700 (PDT) Received: from kientzle.com (h-66-166-149-50.SNVACAID.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4574443F75 for ; Sun, 13 Jul 2003 08:39:34 -0700 (PDT) (envelope-from kientzle@acm.org) Received: from acm.org (ugly.x.kientzle.com [66.166.149.53]) by kientzle.com (8.12.9/8.12.9) with ESMTP id h6DFdRgY024659; Sun, 13 Jul 2003 08:39:27 -0700 (PDT) (envelope-from kientzle@acm.org) Message-ID: <3F117DDB.3000508@acm.org> Date: Sun, 13 Jul 2003 08:42:19 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0.1) Gecko/20021005 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Reynolds References: <16144.55332.161178.446499@whale.home-net> <20030713044837.GA56283@pit.databus.com> <16144.60146.32326.419894@whale.home-net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Barney Wolff cc: current@freebsd.org Subject: Re: build error building cvs doc? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kientzle@acm.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jul 2003 15:39:35 -0000 John Reynolds wrote: > [ On Sunday, July 13, Barney Wolff wrote: ] >>Me too. I'm about to try re-cvsupping, in case I caught some update >>in the middle. > > Somebody else asked if I was doing a "make -jN" buildworld where N > 1 and I > was. So, I just now did a buildworld with one process and it finished just > fine. Strange. > > The only other thing in the original logfile shows: > > make: don't know how to make /usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclient/client/clparse.o. Stop > *** Error code 2 > 1 error > > So, perhaps something related to the above is not "-jN safe". Yes, /rescue is known to be "not -jN safe" I've been trying to puzzle out exactly why and how to fix, but have yet to come up with anything. Suggestions/comments/advice welcome. Tim