From owner-freebsd-arm@freebsd.org Tue Dec 3 16:20:47 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1C0A11B439F for ; Tue, 3 Dec 2019 16:20:47 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 47S6fQ2nMdz4Z0l for ; Tue, 3 Dec 2019 16:20:46 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id xB3GKm8U058828 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 3 Dec 2019 08:20:49 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id xB3GKmGn058827; Tue, 3 Dec 2019 08:20:48 -0800 (PST) (envelope-from fbsd) Date: Tue, 3 Dec 2019 08:20:47 -0800 From: bob prohaska To: greg@unrelenting.technology Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: make -j1 produces four C++ instances Message-ID: <20191203162047.GB58722@www.zefox.net> References: <20191203155514.GA58722@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Rspamd-Queue-Id: 47S6fQ2nMdz4Z0l X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [0.30 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.79)[-0.793,0]; WWW_DOT_DOMAIN(0.50)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; IP_SCORE(0.07)[ip: (0.29), ipnet: 50.1.16.0/20(0.15), asn: 7065(-0.04), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-0.88)[-0.879,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; MID_RHS_WWW(0.50)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Dec 2019 16:20:47 -0000 On Tue, Dec 03, 2019 at 04:06:08PM +0000, greg@unrelenting.technology wrote: > December 3, 2019 6:55 PM, "bob prohaska" wrote: > > > Has the -j feature for make been changed/removed? > > > > IIRC, one could in the past limit the number of jobs created > > while compiling software by using > > make -jN > > on the command line. Now it seems that > > make -j1 > > spawns four instances of C++ while trying to compile www/chromium. > > make -jN won't necessarily do anything when make spawns other build systems > which do their own parallelism. > (*some* systems can integrate with GNU make, see e.g. > https://github.com/ninja-build/ninja/issues/1139 ) > Which leads to: https://github.com/ninja-build/ninja/issues/1441 > Chromium is mostly built using their own GN system, > the backend of which actually is ninja btw > Implying the behavior is controlled by ninja, not make. Is there some other way to restrain parallelism in compiling www/chromium? Thanks for replying! bob prohaska