From owner-freebsd-current@FreeBSD.ORG Fri Jan 2 13:22:31 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 3BFA11065670; Fri, 2 Jan 2009 13:22:31 +0000 (UTC) (envelope-from Johan@double-l.nl) Received: from smtp-vbr8.xs4all.nl (smtp-vbr8.xs4all.nl [194.109.24.28]) by mx1.freebsd.org (Postfix) with ESMTP id C663D8FC1F; Fri, 2 Jan 2009 13:22:30 +0000 (UTC) (envelope-from Johan@double-l.nl) Received: from w2003s01.double-l.local (double-l.xs4all.nl [80.126.205.144]) by smtp-vbr8.xs4all.nl (8.13.8/8.13.8) with ESMTP id n02DMTag036814; Fri, 2 Jan 2009 14:22:30 +0100 (CET) (envelope-from Johan@double-l.nl) MIME-Version: 1.0 Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Fri, 2 Jan 2009 14:24:07 +0100 Message-ID: <57200BF94E69E54880C9BB1AF714BBCB0111B5@w2003s01.double-l.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: build -j3 not working anymore on Current Thread-Index: Acls1mIG/lZGMBvKRyqJm2zGvBNqAAABwGzh References: <57200BF94E69E54880C9BB1AF714BBCB0111B3@w2003s01.double-l.local> <20090102115339.GA81380@in-addr.com> <57200BF94E69E54880C9BB1AF714BBCB5DE3C6@w2003s01.double-l.local> <20090102123051.GB81380@in-addr.com> From: "Johan Hendriks" To: "Gary Palmer" X-Virus-Scanned: by XS4ALL Virus Scanner Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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 13:22:31 -0000 >>=20 >> Hello >>=20 >> 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.=20 >> At least at the amd64 host, the i386 is still building, it takes some = time on a PIII ;-) >>=20 >> So I have no idea where the error message kicks in. >>=20 >> 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 i also found the following error lines. crunchgen: make error: --- crunchgen_objs --- crunchgen: make error: --- loop --- Run "make -f rescue.mk" to build crunched binary. *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 regards, Johan Hendriks