unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Building cvs emacs on a dual-core machine
Date: Wed, 20 Dec 2006 20:54:15 +0200	[thread overview]
Message-ID: <u64c6mm94.fsf@gnu.org> (raw)
In-Reply-To: <emb7s0$gh9$1@sea.gmane.org> (message from Eric Lilja on Wed, 20 Dec 2006 12:47:13 +0100)

> From: Eric Lilja <mindcooler@gmail.com>
> Date: Wed, 20 Dec 2006 12:47:13 +0100
> 
> 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.

Any such failures are bugs in the Emacs Makefiles, so please be sure
to report them with full details, including the build log.

If you didn't try this with the CVS version or with the latest
pretest, please do try one of these, because many problems present in
Emacs 21.x are already resolved in the latest development code.

Thanks in advance.

> 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?

A bug-free Makefile should never cause any such trouble, since all the
dependencies are supposed to be spelled out in it, and Make will never
start building a file until all its prerequisites are built.

  parent reply	other threads:[~2006-12-20 18:54 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20 11:47 Building cvs emacs on a dual-core machine Eric Lilja
2006-12-20 14:40 ` 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 [this message]
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=u64c6mm94.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@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.
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).