From owner-freebsd-current@FreeBSD.ORG Fri Jan 2 12:30:53 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D18B106566C for ; Fri, 2 Jan 2009 12:30:53 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (mail.in-addr.com [IPv6:2001:470:8:162::1]) by mx1.freebsd.org (Postfix) with ESMTP id E8FA28FC20 for ; Fri, 2 Jan 2009 12:30:52 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by noop.in-addr.com with local (Exim 4.54 (FreeBSD)) id 1LIjAy-000OHw-1Y; Fri, 02 Jan 2009 07:30:52 -0500 Date: Fri, 2 Jan 2009 07:30:51 -0500 From: Gary Palmer To: Johan Hendriks Message-ID: <20090102123051.GB81380@in-addr.com> References: <57200BF94E69E54880C9BB1AF714BBCB0111B3@w2003s01.double-l.local> <20090102115339.GA81380@in-addr.com> <57200BF94E69E54880C9BB1AF714BBCB5DE3C6@w2003s01.double-l.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <57200BF94E69E54880C9BB1AF714BBCB5DE3C6@w2003s01.double-l.local> Cc: freebsd-current@freebsd.org Subject: Re: build -j3 not working anymore on Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 02 Jan 2009 12:30:53 -0000 On Fri, Jan 02, 2009 at 01:01:07PM +0100, Johan Hendriks wrote: > > Hello > > If you read on after the error message in my mail you will see that a buildworld cycle without the -j3 option works so I get no error message that way ;-) Johan, Sorry, missed that bit. > At least at the amd64 host, the i386 is still building, it takes some time on a PIII ;-) > > So I have no idea where the error message kicks in. > > Is there a way to get the error message? >From memory: If you have the build output in a log file, look for '**' at the start of the line. If you look around where you find the '**' you should hopefully find the error messages. Regards, Gary