From owner-freebsd-questions@FreeBSD.ORG Sat Mar 3 12:35:19 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B48D516A401 for ; Sat, 3 Mar 2007 12:35:19 +0000 (UTC) (envelope-from news@nermal.rz1.convenimus.net) Received: from mx1.netclusive.de (mx1.netclusive.de [89.110.132.131]) by mx1.freebsd.org (Postfix) with ESMTP id 79FAD13C471 for ; Sat, 3 Mar 2007 12:35:19 +0000 (UTC) (envelope-from news@nermal.rz1.convenimus.net) Received: from nermal.rz1.convenimus.net (Fdd20.f.ppp-pool.de [195.4.221.32]) by mx1.netclusive.de (Postfix) with ESMTP id EF2ABDE8010 for ; Sat, 3 Mar 2007 13:35:17 +0100 (CET) Received: by nermal.rz1.convenimus.net (Postfix, from userid 8) id D214215213; Sat, 3 Mar 2007 13:35:14 +0100 (CET) To: freebsd-questions@freebsd.org Path: not-for-mail From: Christian Baer Newsgroups: gmane.os.freebsd.questions Date: Sat, 3 Mar 2007 13:35:14 +0100 (CET) Organization: Convenimus Projekt Lines: 14 Message-ID: References: <200702281044.16855.josh@tcbug.org> <44hct617hf.fsf@be-well.ilk.org> NNTP-Posting-Host: garfield.rz1.convenimus.net X-Trace: nermal.rz1.convenimus.net 1172925314 99267 192.168.100.11 (3 Mar 2007 12:35:14 GMT) X-Complaints-To: abuse@convenimus.net NNTP-Posting-Date: Sat, 3 Mar 2007 12:35:14 +0000 (UTC) User-Agent: slrn/0.9.8.1 (FreeBSD) Subject: Re: compiling ports with more than one job X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2007 12:35:19 -0000 On Wed, 28 Feb 2007 13:07:24 -0500 Lowell Gilbert wrote: > Exactly right. However, you can get some parallel building by doing > more than one single-threaded build at the same time. This leads to > some danger of corrupting the database, though, so it's not for the > squeamish. I know that portupgrade uses locking to control those > problems, and I suspect some of the other port-management ports > probably have similar capabilities. That could actually lead to more problems than a port that doesn't work with -jX. Regards Chris