unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Bill Wohler <wohler@newt.com>
To: emacs-pretest-bug@gnu.org
Cc: bug-gnu-emacs@gnu.org
Subject: bug#1705: 23.0.60; parallel build failure: `mh-e' was not provided
Date: Fri, 02 Jan 2009 11:34:40 -0800	[thread overview]
Message-ID: <87k59dtsbz.fsf@olgas.newt.com> (raw)
In-Reply-To: jwv3ag5t6vj.fsf-monnier+emacsbugreports@gnu.org

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> I added to lisp/Makefile.in a series of dependencies that should fix
>> the case of MH-E compilation.  Please see if this fixes the problem
>> for you.  If you have more than 2 processors, it would make sense to
>> try "make -j N" with values of N larger than 2, to increase the
>> probability of such a clash.
>
> This won't solve it in general, because there are many circular
> dependencies among Elisp files.  Another approach is to just close the
> race condition: write the byte-compiled file to foo.elc.temp and then
> rename it atomically to foo.elc.

Thanks Eli and Stefan. My laptop isn't a multi-processor box (yet) so
I can't be of more assistance. All I can say is that with the last big
MH-E reorganization going into MH-E 8.0, we eliminated all circular
dependencies within MH-E. I can't speak for the packages we require,
however.

-- 
Bill Wohler <wohler@newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD







  reply	other threads:[~2009-01-02 19:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-25 22:27 bug#1705: 23.0.60; parallel build failure: `mh-e' was not provided Markus Triska
2008-12-27 12:19 ` Eli Zaretskii
2008-12-31  2:30   ` Stefan Monnier
2009-01-02 19:34     ` Bill Wohler [this message]
2009-01-03  9:22     ` Eli Zaretskii
2009-01-05  4:12       ` Stefan Monnier
2009-01-05 20:00         ` Eli Zaretskii
2009-01-05 22:21           ` Stefan Monnier
2009-01-06  4:06             ` Eli Zaretskii
2009-01-06 15:00               ` Stefan Monnier
2009-01-06 20:36                 ` Eli Zaretskii
2009-01-06 22:15                   ` Stefan Monnier
2009-01-06 12:31             ` Richard M 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=87k59dtsbz.fsf@olgas.newt.com \
    --to=wohler@newt.com \
    --cc=1705@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=emacs-pretest-bug@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).