From owner-freebsd-current@FreeBSD.ORG Fri Jan 2 12:01:16 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 3CFB11065670 for ; Fri, 2 Jan 2009 12:01:16 +0000 (UTC) (envelope-from Johan@double-l.nl) Received: from smtp-vbr13.xs4all.nl (smtp-vbr13.xs4all.nl [194.109.24.33]) by mx1.freebsd.org (Postfix) with ESMTP id CB9708FC1D for ; Fri, 2 Jan 2009 12:01:15 +0000 (UTC) (envelope-from Johan@double-l.nl) Received: from w2003s01.double-l.local (double-l.xs4all.nl [80.126.205.144]) by smtp-vbr13.xs4all.nl (8.13.8/8.13.8) with ESMTP id n02C16lh015851; Fri, 2 Jan 2009 13:01:14 +0100 (CET) (envelope-from Johan@double-l.nl) MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: quoted-printable Content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Fri, 2 Jan 2009 13:01:07 +0100 Message-ID: <57200BF94E69E54880C9BB1AF714BBCB5DE3C6@w2003s01.double-l.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: build -j3 not working anymore on Current Thread-Index: Acls0TI9HkPoOVWpTIqkGi+dB1kSgAAAB5Ug References: <57200BF94E69E54880C9BB1AF714BBCB0111B3@w2003s01.double-l.local> <20090102115339.GA81380@in-addr.com> From: "Johan Hendriks" To: "Gary Palmer" X-Virus-Scanned: by XS4ALL Virus Scanner 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:01:16 -0000 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 ;-) 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? Regards, Johan Hendriks No virus found in this outgoing message. Checked by AVG - http://www.avg.com=20 Version: 8.0.176 / Virus Database: 270.10.2/1871 - Release Date: = 1-1-2009 17:01