From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
joakim@verona.se, emacs-devel@gnu.org
Subject: Re: revno 101399 fails to build
Date: Mon, 13 Sep 2010 17:52:59 +0200 [thread overview]
Message-ID: <jwvfwxdtzgb.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83vd695096.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 13 Sep 2010 13:52:21 +0200")
>> > ...
>> > In toplevel form:
>> > calc/calc-help.el:30:1:Error: Required feature `calc-ext' was not provided
>>
>> Do you build with more that one job in parallel? In this case it can
>> happen that one emacs process writes out the elc file while another one
>> is reading the same (partial) file at the same time. To fix that the
>> creation of the elc file need to be made atomic.
> Or specify explicit dependencies in the Makefile. Or get Emacs to
> generate such dependencies given the `require's.
BTW, I did play with that a long time ago and the result was that it
works to some extent but it's not enough: many dependencies come from
autoloaded functions/macros, there are circular require-dependencies,
many dependencies come from preloaded files without any `require'
in sight.
Maybe a more promising direction is to let the byte-compiler emit
dependencies as it goes, just like gcc can do.
Stefan
next prev parent reply other threads:[~2010-09-13 15:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 5:40 revno 101399 fails to build joakim
2010-09-10 6:27 ` Glenn Morris
2010-09-10 7:48 ` joakim
2010-09-11 4:58 ` Stephen J. Turnbull
2010-09-13 12:08 ` Eli Zaretskii
2010-09-14 12:22 ` Stephen J. Turnbull
2010-09-10 8:37 ` Andreas Schwab
2010-09-10 8:52 ` joakim
2010-09-13 11:52 ` Eli Zaretskii
2010-09-13 15:52 ` Stefan Monnier [this message]
2010-09-13 17:05 ` Eli Zaretskii
2010-09-13 16:17 ` Glenn Morris
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=jwvfwxdtzgb.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
--cc=schwab@linux-m68k.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).