From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Two strange messages while building Emacs on MS-Windows Date: Sat, 08 Dec 2012 11:24:16 +0200 Message-ID: <834njwnbgf.fsf@gnu.org> References: <83mwxpmtp6.fsf@gnu.org> <83fw3hm0nn.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1354958685 1295 80.91.229.3 (8 Dec 2012 09:24:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 8 Dec 2012 09:24:45 +0000 (UTC) Cc: emacs-devel@gnu.org To: Dani Moncayo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 08 10:24:58 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ThGeX-0001Ci-I5 for ged-emacs-devel@m.gmane.org; Sat, 08 Dec 2012 10:24:57 +0100 Original-Received: from localhost ([::1]:48913 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ThGeK-0004Um-HD for ged-emacs-devel@m.gmane.org; Sat, 08 Dec 2012 04:24:44 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:45952) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ThGeH-0004Ub-73 for emacs-devel@gnu.org; Sat, 08 Dec 2012 04:24:43 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ThGeG-0007U8-9A for emacs-devel@gnu.org; Sat, 08 Dec 2012 04:24:41 -0500 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:41990) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ThGeG-0007Tx-0q for emacs-devel@gnu.org; Sat, 08 Dec 2012 04:24:40 -0500 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0MEP00H00GI07S00@a-mtaout20.012.net.il> for emacs-devel@gnu.org; Sat, 08 Dec 2012 11:24:33 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MEP00GOZGSVUEB0@a-mtaout20.012.net.il>; Sat, 08 Dec 2012 11:24:32 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.166 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:155362 Archived-At: > Date: Sat, 8 Dec 2012 09:43:22 +0100 > From: Dani Moncayo > Cc: emacs-devel@gnu.org > > I'll try a parallel build. BTW, a plain "-j" option seem to be a good > choice; according to the GNU Make manual it will dynamically > determine how many parallel recipes can be run: > > `-j [JOBS]' > `--jobs[=JOBS]' > Specifies the number of recipes (jobs) to run simultaneously. > With no argument, `make' runs as many recipes simultaneously as > possible. If there is more than one `-j' option, the last one is > effective. *Note Parallel Execution: Parallel, for more > information on how recipes are run. Note that this option is > ignored on MS-DOS. Read more. In the referenced node, the manual says: If the `-j' option is followed by an integer, this is the number of recipes to execute at once; this is called the number of "job slots". If there is nothing looking like an integer after the `-j' option, there is no limit on the number of job slots. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ That's it. Nothing as sophisticated as you seem to have concluded. On Windows, "no limit" means "-j 64", because that's the limitation of the API used on Windows to watch child processes. (The referenced node also describes the -l option, which could limit the effective number of parallel jobs depending on the system load, but since sensing the system load doesn't work on Windows, that option is of no use for you.) So I suggest to time different "-j N" bootstraps and find the one that is the fastest. Or just use the recipe I gave ;-)