From owner-freebsd-stable@FreeBSD.ORG Fri Sep 20 17:06:53 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8CE08198; Fri, 20 Sep 2013 17:06:53 +0000 (UTC) (envelope-from illoai@gmail.com) Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6227A23C2; Fri, 20 Sep 2013 17:06:53 +0000 (UTC) Received: by mail-pd0-f180.google.com with SMTP id y10so620464pdj.11 for ; Fri, 20 Sep 2013 10:06:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9bSt65qK2EYzJgkP4dGAEZ3uXOJspP/JZ68TEOYpufQ=; b=YhED3peB1I3HfCQ3HkZrRyVjjQgSDbYo261FVCAXlmu9nPYveOss5yo8tQrSdHlDdm qquarRL+lCiD7b2HDdvJolNema9xUcIwq5/O2NgDZA5ktmoAekJ3T6Z4KaB00/gIeGxV lci+hmxuQN6r+00YkJr83HuREBaSDn9SNNdtuMYSf8K43qRBnoDb1/zXZMElTqmsh7c4 moTHJnlH6MTZRidVV/zKahamVFHoG4E9gYFnZ3xT8I3qch+sJXz8xYp+gfEnQ7iPbBMT 2U+i8VDFI+owwmDdE29xkSVJTosOt+FEWzOpBcAoZo+3blMTP/2Mdm66BoSn+u+AWCRz a3FQ== MIME-Version: 1.0 X-Received: by 10.68.90.129 with SMTP id bw1mr9078431pbb.111.1379696812963; Fri, 20 Sep 2013 10:06:52 -0700 (PDT) Received: by 10.68.133.202 with HTTP; Fri, 20 Sep 2013 10:06:52 -0700 (PDT) In-Reply-To: <20130920155208.GA55143@in-addr.com> References: <523AFF46.29244.4657A1@lausts.acm.org> <523B91F2.8070004@heuristicsystems.com.au> <523C49A9.5719.289C1E@lausts.acm.org> <20130920143615.GA40029@in-addr.com> <20130920144928.GA50355@mail.laus.org> <20130920155208.GA55143@in-addr.com> Date: Fri, 20 Sep 2013 13:06:52 -0400 Message-ID: Subject: Re: FreeBSD 9-Stable + Atom D510 Freeze From: "illoai@gmail.com" To: Gary Palmer Content-Type: text/plain; charset=ISO-8859-1 Cc: ml-freebsd-stable , Thomas Laus X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Sep 2013 17:06:53 -0000 On 20 September 2013 11:52, Gary Palmer wrote: > On Fri, Sep 20, 2013 at 10:49:28AM -0400, Thomas Laus wrote: >> Gary Palmer [gpalmer@freebsd.org] wrote: >> > >> > When building kernel & world do you use the '-j' argument to do parallel >> > builds? AFAIK thats not done by default, but it is for some ports. >> > >> Gary: >> >> I just use the system defaults when building anything. If there is a >> '-j' argument passed to the compiler, I was not the one that did it. >> Does this mean that the port building process needs to determine the >> processor type in the configure stage? I only use portmaster to keep >> the ports updated. I don't know of a global hook that will change the >> compiler build flags in portmaster. > > Hi Tim, > > It's not a compiler flag, it's a make flag. make -j n will fork off up to > n compilers to do the build. If you just do "make buildworld" then there > is no parallel compilation. > > It used to be that ports had MAKE_JOBS_SAFE in the Makefile to mark that > the port could be built using parallel compiles with the '-j' argument > to make. It appears that the logic has been switched and now you have > to mark them as MAKE_JOBS_UNSAFE to say that parallel builds shouldn't be > done, indicating that parallel builds are the default now (unless I'm > misreading the code) > > You can try putting > > DISABLE_MAKE_JOBS=yes > > into /etc/make.conf to see if that stops the problem on port builds. > Alternatively I think you could do > > portmaster -m DISABLE_MAKE_JOBS=yes > > However you'd have to do that each time you run portmaster. I think > putting > > PM_MAKE_ARGS="DISABLE_MAKE_JOBS=yes" > > in your .portmasterrc may do the same thing (not tried it). > > Note: this is NOT a fix. If it works, it merely stops the ports builder > from triggering the problem by not doing parallel compiles. The compiles > will also take longer. > I believe that both world/kernel & ports will honour MAKE_JOBS_NUMBER=1 #(in /etc/make.conf) which should restrict all builds to 1 "parallel" thread, yes? -- --