From: Eli Zaretskii <eliz@gnu.org>
Cc: mindcooler@gmail.com, emacs-devel@gnu.org, storm@cua.dk
Subject: Re: Building cvs emacs on a dual-core machine
Date: Fri, 22 Dec 2006 23:37:44 +0200 [thread overview]
Message-ID: <umz5flihj.fsf@gnu.org> (raw)
In-Reply-To: <m2y7p0nger.fsf@chrislap.local> (message from Chris Moore on Fri, 22 Dec 2006 15:39:40 +0100)
> Cc: storm@cua.dk (Kim F. Storm), mindcooler@gmail.com, emacs-devel@gnu.org
> From: Chris Moore <dooglus@gmail.com>
> Date: Fri, 22 Dec 2006 15:39:40 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > There's nothing to prevent a parallel build from compiling 2 Lisp
> > files at the same time, is there?
>
> Yes, there is, at least on GNU/Linux make isn't used to determine
> which Lisp files to compile.
>
> During bootstrapping, it's done using the shell:
>
> [...] for el in [...] $els; do echo Compiling $el; [...]; done
>
> and during 'make recompile', it's done using emacs itself:
>
> ../src/emacs -batch --no-site-file --multibyte --eval
> (batch-byte-recompile-directory 0) /home/chris/programs/emacs2/lisp
>
> Neither of these will honour make's --jobs=2 flag.
It's true that lisp/Makefile.in doesn't give much chance to exploit
parallelism, but it's not true that no parallelism is possible there.
`compile', `recompile', and `cvs-update' have prerequisites that can
be produced in parallel.
leim/Makefile.in is better organized for parallel make, and it's not
inconceivable to have Emacs compile in parallel in lisp/ and in leim/.
next prev parent reply other threads:[~2006-12-22 21:37 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 [this message]
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=umz5flihj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mindcooler@gmail.com \
--cc=storm@cua.dk \
/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).