From owner-freebsd-current@FreeBSD.ORG Thu Jul 22 19:05:21 2004 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 3841A16A4CE for ; Thu, 22 Jul 2004 19:05:21 +0000 (GMT) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6C5943D2F for ; Thu, 22 Jul 2004 19:05:20 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from [207.41.94.233] (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id i6MJ4EH5030430; Thu, 22 Jul 2004 12:04:15 -0700 From: Kent Stewart To: freebsd-current@freebsd.org Date: Thu, 22 Jul 2004 12:05:18 -0700 User-Agent: KMail/1.6.2 References: <021001c46e97$84c05210$471b3dd4@digiware.nl> <01ea01c46fc8$6d1f32c0$471b3dd4@digiware.nl> <20040722114523.C92369@carver.gumbysoft.com> In-Reply-To: <20040722114523.C92369@carver.gumbysoft.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407221205.18540.kstewart@owt.com> Subject: Re: Erros in: make -j 16 buildword X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jul 2004 19:05:21 -0000 On Thursday 22 July 2004 11:47 am, Doug White wrote: > On Thu, 22 Jul 2004, Willem Jan Withagen wrote: > > From: "Doug White" > > > > > On Tue, 20 Jul 2004, Willem Jan Withagen wrote: > > > > Hi, > > > > > > > > One way or another it seems that I can no longer buildworld > > > > with -j16. -j8 works perfectly, but -j16 fails consistently at: > > > > > > [...] > > > > > > > Unless anybody has suggestions of which programs generate these > > > > tearse messages??? > > > > Or a way to get make to be more informative??? > > > > > > You need to capture the entire output since the error is buried > > > in there. Make doesn't abort -j builds until all the subprocesses > > > are finished, and they can run for a long time... > > > > You know how long the output of a buildworld is, right?? > > When the errors are reported, visually it is at the point where it > > normally looks like it is done. > > Its not that bad. There's a large number of people that log their > builds, and besides, diskspace is cheap! I am one of these people. I figure that if you don't log, then you must think your time isn't worth anything because you have to rerun it to log the problem. I created a directory called /var/log/build to hold the logs. I don't have any MP systems and -j* was always slower than no -j. With a no -j log, you don't have to rerun the build to find the problem. I never seem to have enough of "me-time" but the system doesn't care what it does :). Kent > > > Building ports gives you notice of the directory in which it > > started to come up from thus telling you which package was in > > error..... > > Port builds aren't done in parallel. The error was printed at the > point of the error, but it doesn't cause all the other subprocesses > to be killed immediately, so they run to completion. > > > Maybe I'll see if I can put something like this in make of the > > makefiles.... > > Good luck... -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html