From: Nordlöw <per.nordlow@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Getting Number of CPU(-core)s and giving it as the --jobs argument to GNU Make
Date: Tue, 11 Sep 2007 07:53:18 -0700 [thread overview]
Message-ID: <1189522398.029390.27390@50g2000hsm.googlegroups.com> (raw)
How can I, from within Emacs in a platform independent way, read out
the number of CPUs/cores my local machine has? I then believe it
should be convenient to give this argument to make (through the -j,--
jobs flag). Thus we will always get full utilization when compiling on
multi-CPU/core machines.
Thanks,
Nordlöw
next reply other threads:[~2007-09-11 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 14:53 Nordlöw [this message]
2007-09-11 17:16 ` Getting Number of CPU(-core)s and giving it as the --jobs argument to GNU Make Peter Dyballa
2007-09-11 20:20 ` Dieter Wilhelm
2007-09-11 21:52 ` Peter Dyballa
2007-09-11 22:11 ` Dieter Wilhelm
2007-09-11 22:29 ` Peter Dyballa
[not found] ` <mailman.725.1189541941.18990.help-gnu-emacs@gnu.org>
2007-09-12 6:30 ` Unknown
2007-09-12 8:20 ` Nordlöw
2007-09-12 9:38 ` Peter Dyballa
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=1189522398.029390.27390@50g2000hsm.googlegroups.com \
--to=per.nordlow@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).