From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 1705@emacsbugs.donarmstrong.com, bug-gnu-emacs@gnu.org,
markus.triska@gmx.at, emacs-pretest-bug@gnu.org
Subject: bug#1705: 23.0.60; parallel build failure: `mh-e' was not provided
Date: Sat, 03 Jan 2009 11:22:53 +0200 [thread overview]
Message-ID: <u8wpsoiaa.fsf@gnu.org> (raw)
In-Reply-To: <jwv3ag5t6vj.fsf-monnier+emacsbugreports@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: 1705@emacsbugs.donarmstrong.com, Markus Triska <markus.triska@gmx.at>, emacs-pretest-bug@gnu.org, bug-gnu-emacs@gnu.org
> Date: Tue, 30 Dec 2008 21:30:33 -0500
>
> > 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.
But adding dependencies is TRT on its own right, even if your
alternative is adopted. As long as the byte compiler cannot grok
those dependencies by itself, that is.
next prev parent reply other threads:[~2009-01-03 9:22 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
2009-01-03 9:22 ` Eli Zaretskii [this message]
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=u8wpsoiaa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=1705@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=markus.triska@gmx.at \
--cc=monnier@iro.umontreal.ca \
/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).