From owner-freebsd-stable@FreeBSD.ORG Fri Oct 13 19:31:59 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76E1C16A412 for ; Fri, 13 Oct 2006 19:31:59 +0000 (UTC) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: from mail1.sea5.speakeasy.net (mail1.sea5.speakeasy.net [69.17.117.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA1CB43D6B for ; Fri, 13 Oct 2006 19:31:52 +0000 (GMT) (envelope-from freebsd-stable-local@be-well.ilk.org) Received: (qmail 16748 invoked from network); 13 Oct 2006 19:31:52 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail1.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 13 Oct 2006 19:31:52 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 1A4EC2842E; Fri, 13 Oct 2006 15:31:48 -0400 (EDT) To: Buki References: <20061013143130.GW491@dev.null.cz> From: Lowell Gilbert Date: Fri, 13 Oct 2006 15:31:48 -0400 In-Reply-To: <20061013143130.GW491@dev.null.cz> (Buki's message of "Fri, 13 Oct 2006 16:31:30 +0200") Message-ID: <44lknkc8rf.fsf@be-well.ilk.org> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD and "make -j# buildworld" usability X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2006 19:31:59 -0000 Buki writes: > I searched the archives and web a little but found many different opinions > on stability/usability of using make -j# with buildworld (and buildkernel). > > So I am asking if it is a good idea to use make -j on production boxes. In addition to all of the other comments, there is one more point to make clear; although parallel builds work fine, they obscure the output from the different paths of the build. Therefore, if you have trouble with a "-j" buildworld, the first thing you need to do is to run it again without the "-j". This is not because it might work that way, but because the error messages will be much easier to understand.