From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Parallel builds with loaddefs removed
Date: Sat, 22 Jun 2013 22:26:25 -0400 [thread overview]
Message-ID: <jwvd2rd7eoo.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83hagplrck.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 23 Jun 2013 01:20:59 +0300")
> If they were not touched and cl-loaddefs.el does not exist, the rule
> will fire and create it.
And what I'm saying is that this is not the case: the rule will fire,
but it will not create cl-loaddefs.el, or maybe it will partly but
not completely, because the autoload.el code will mostly compare the
timestamp in lisp/loaddefs.el with the mtime of the cl-*.el files and
only consult those that are more recent, and only those so consulted
will see their autoloads added to cl-loaddefs.
> If they were touched, the rule will fire and
> update cl-loaddefs.el.
If they were touched, then the comparison with the lisp.loaddefs.el
timestamp will indeed cause them to be scanned, so their autoloads will
end up in cl-loaddefs.el. But if they were not all touched, then only
some of them will be consulted, so the cl-loaddefs.el will end up
incomplete.
Stefan
next prev parent reply other threads:[~2013-06-23 2:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 15:19 Parallel builds with loaddefs removed Eli Zaretskii
2013-06-21 15:30 ` Stefan Monnier
2013-06-21 15:56 ` Eli Zaretskii
2013-06-21 18:57 ` Stefan Monnier
2013-06-21 19:13 ` Eli Zaretskii
2013-06-21 19:56 ` Stefan Monnier
2013-06-22 9:36 ` Eli Zaretskii
2013-06-22 15:15 ` Stefan Monnier
2013-06-22 15:25 ` Eli Zaretskii
2013-06-22 19:20 ` Stefan Monnier
2013-06-22 22:20 ` Eli Zaretskii
2013-06-23 2:26 ` Stefan Monnier [this message]
2013-06-21 19:20 ` Glenn Morris
2013-06-21 19:28 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvd2rd7eoo.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.