From: Eric Lilja <mindcooler@gmail.com>
Subject: Building cvs emacs on a dual-core machine
Date: Wed, 20 Dec 2006 12:47:13 +0100 [thread overview]
Message-ID: <emb7s0$gh9$1@sea.gmane.org> (raw)
Hi!
I recently upgraded my computer with a dual-core CPU. I've been enjoying
nice decreases in compile time in my own projects by specifying --jobs=2
when invoking make.
However, when I tried that with emacs it started compiling, very fast
with both cores busy, but the build craps out (sorry, no log) after a
little while. Maybe because it tries to build something that depends on
something else that has not been quite finished yet because when
multiple jobs are specified things doesn't happen in serial anymore? I
don't know, but I know it works if I exclude --jobs=2. But then emacs is
built and the total cpu utilization is only 50 percent. :-( Is there a
way I can utilise both cores when building emacs? I bought the new
processor mostly to get improved compile time performace. :-)
- Eric
next reply other threads:[~2006-12-20 11:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 11:47 Eric Lilja [this message]
2006-12-20 14:40 ` Building cvs emacs on a dual-core machine Kim F. Storm
2006-12-20 19:05 ` Eli Zaretskii
2006-12-21 11:04 ` Kim F. Storm
2006-12-22 14:39 ` Chris Moore
2006-12-22 21:37 ` Eli Zaretskii
2006-12-22 23:39 ` Chris Moore
2006-12-20 18:54 ` Eli Zaretskii
2006-12-20 19:48 ` Eric Lilja
2006-12-20 21:03 ` Eric Lilja
2006-12-20 23:27 ` Eli Zaretskii
2006-12-21 0:14 ` Eric Lilja
2006-12-22 21:50 ` Eli Zaretskii
2006-12-22 23:30 ` Eric Lilja
2006-12-23 1:50 ` Eli Zaretskii
2006-12-23 2:04 ` Eric Lilja
2006-12-23 10:42 ` Eli Zaretskii
2006-12-23 10:59 ` Eric Lilja
2006-12-23 11:24 ` Eric Lilja
2006-12-23 12:46 ` Eli Zaretskii
2007-01-03 20:56 ` Eric Lilja
2007-01-04 4:15 ` Eli Zaretskii
2007-01-04 20:17 ` Randal L. Schwartz
2007-01-04 21:59 ` Eli Zaretskii
2006-12-23 1:54 ` Juanma Barranquero
2006-12-23 9:53 ` Eli Zaretskii
2006-12-20 22:19 ` Richard Stallman
2006-12-26 19:22 ` Randal L. Schwartz
2006-12-27 21:16 ` Richard Stallman
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='emb7s0$gh9$1@sea.gmane.org' \
--to=mindcooler@gmail.com \
/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).