unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <ghe@sdf.org>
Cc: larsi@gnus.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Script for compiling more quietly
Date: Mon, 14 Dec 2020 18:49:32 +0200	[thread overview]
Message-ID: <83zh2gbaeb.fsf@gnu.org> (raw)
In-Reply-To: <alpine.NEB.2.22.394.2012141700570453.15506@sdf.lonestar.org> (emacs-devel@gnu.org)

> Date: Mon, 14 Dec 2020 16:07:04 +0000
> Cc: larsi@gnus.org, Stefan Monnier <monnier@iro.umontreal.ca>,
>  emacs-devel@gnu.org
> From: Gregory Heytings via "Emacs development discussions." <emacs-devel@gnu.org>
> 
> > FWIW, I think you should leave the N part of "make -jN" to the end user. 
> > No one said they have nothing else to do at the same time as they build 
> > Emacs; they could be building some other large program at the same time, 
> > or need the CPU for something else.
> 
> It is, the number of cores is just a default value, that can be overridden 
> by "emake -j1" for instance.

In which case I don't understand why it is important to be accurate
with the actual number of cores.  You could just use 4 as the default.



  reply	other threads:[~2020-12-14 16:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11 18:10 Script for compiling more quietly Lars Ingebrigtsen
2020-12-14 10:32 ` Gregory Heytings via Emacs development discussions.
2020-12-14 10:52   ` Gregory Heytings via Emacs development discussions.
2020-12-14 14:35   ` Lars Ingebrigtsen
2020-12-14 15:08     ` Lars Ingebrigtsen
2020-12-14 14:39   ` Lars Ingebrigtsen
2020-12-14 15:09     ` Gregory Heytings via Emacs development discussions.
2020-12-14 15:23       ` Stefan Monnier
2020-12-14 15:28         ` Gregory Heytings via Emacs development discussions.
2020-12-14 15:56         ` Eli Zaretskii
2020-12-14 16:07           ` Gregory Heytings via Emacs development discussions.
2020-12-14 16:49             ` Eli Zaretskii [this message]
2020-12-14 16:53               ` Lars Ingebrigtsen
2020-12-14 17:24                 ` Andrea Corallo via Emacs development discussions.
2020-12-14 17:55                   ` Eli Zaretskii
2020-12-14 17:41                 ` Gregory Heytings via Emacs development discussions.
2020-12-14 18:56                   ` Lars Ingebrigtsen
2020-12-14 17:49                 ` Eli Zaretskii
2020-12-14 23:36                   ` Stefan Monnier
2020-12-14 15:00   ` Stefan Monnier
2020-12-14 15:14     ` Gregory Heytings via Emacs development discussions.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83zh2gbaeb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ghe@sdf.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).