From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: bootstrap not regenerating some *loaddefs
Date: Fri, 20 Jun 2008 16:15:35 -0400 [thread overview]
Message-ID: <2x3an73lso.fsf@fencepost.gnu.org> (raw)
In-Reply-To: uy74zgae7.fsf@gnu.org
Eli Zaretskii wrote:
> Please trust me that I did so before asking the question. I simply
> don't understand what you are saying there, perhaps because most of
> that comment doesn't describe the present solution, but rather
> different alternatives that were not taken.
Sorry both for doubting you and for being unclear. :)
The reason for making custom-deps and finder-data depend on loaddefs
was that these rules used to scan _all_ the *.el files. This included
loaddefs and friends. In a parallel make, loaddefs etc could be
changed while custom-deps/finder-data were trying to read them. (I
think you know this bit.)
Since there is no useful information for custom-deps/finder-data in
loaddefs etc, I made custom-make-dependencies and
finder-compile-keywords-make-dist not scan these files any more (see
finder-no-scan-regexp etc). So to answer your original question,
custom-deps/finder-data indeed no longer scan _all_ *.el files, so
should no longer care if loaddefs etc are modified while they run.
Making these rules depend on loaddefs had undesirable side effects, as
described in the comments, so it was good to remove this.
I have tested this with `make -j4 updates', the source of the original
problem.
next prev parent reply other threads:[~2008-06-20 20:15 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 11:57 bootstrap not regenerating some *loaddefs Juanma Barranquero
2008-06-17 15:13 ` Jason Rumney
2008-06-17 16:19 ` Juanma Barranquero
2008-06-17 16:38 ` Glenn Morris
2008-06-17 17:43 ` Juanma Barranquero
2008-06-17 17:46 ` Glenn Morris
2008-06-17 17:55 ` Juanma Barranquero
2008-06-17 18:05 ` Juanma Barranquero
2008-06-17 19:01 ` Juanma Barranquero
2008-06-17 21:05 ` Stefan Monnier
2008-06-18 14:23 ` Juanma Barranquero
2008-06-18 15:20 ` Stefan Monnier
2008-06-18 15:51 ` Juanma Barranquero
2008-06-18 16:47 ` Glenn Morris
2008-06-18 16:59 ` Juanma Barranquero
2008-06-18 18:18 ` Eli Zaretskii
2008-06-19 6:23 ` Glenn Morris
2008-06-19 8:28 ` Juanma Barranquero
2008-06-19 19:13 ` Glenn Morris
2008-06-19 19:38 ` Juanma Barranquero
2008-06-19 20:51 ` Stefan Monnier
2008-06-20 4:17 ` Glenn Morris
2008-06-20 7:49 ` Juanma Barranquero
2008-06-20 18:13 ` Glenn Morris
2008-06-20 7:54 ` Jason Rumney
2008-06-20 7:58 ` Juanma Barranquero
2008-06-20 9:16 ` Eli Zaretskii
2008-06-20 17:46 ` Glenn Morris
2008-06-20 19:43 ` Eli Zaretskii
2008-06-20 20:15 ` Glenn Morris [this message]
2008-06-20 21:25 ` Stefan Monnier
2008-06-20 22:46 ` Glenn Morris
2008-06-21 7:10 ` Eli Zaretskii
2008-06-21 19:37 ` Glenn Morris
2008-06-18 18:12 ` Eli Zaretskii
2008-06-18 18:18 ` Juanma Barranquero
2008-06-19 0:20 ` Miles Bader
2008-06-19 0:36 ` Juanma Barranquero
2008-06-19 3:15 ` Eli Zaretskii
2008-06-19 8:23 ` Juanma Barranquero
2008-06-19 10:53 ` Juanma Barranquero
2008-06-19 19:02 ` Eli Zaretskii
2008-06-19 22:44 ` Juanma Barranquero
2008-06-20 8:45 ` Eli Zaretskii
2008-06-20 9:27 ` Juanma Barranquero
2008-06-20 9:49 ` Eli Zaretskii
2008-06-20 10:03 ` Jason Rumney
2008-06-20 10:19 ` Eli Zaretskii
2008-06-20 10:37 ` Jason Rumney
2008-06-20 9:50 ` Eli Zaretskii
2008-06-20 10:30 ` Juanma Barranquero
2008-06-20 10:48 ` Eli Zaretskii
2008-06-20 11:10 ` Juanma Barranquero
2008-06-20 11:12 ` Juanma Barranquero
2008-06-20 12:02 ` Eli Zaretskii
2008-06-20 13:24 ` Juanma Barranquero
2008-06-20 14:29 ` Eli Zaretskii
2008-06-20 15:06 ` Juanma Barranquero
2008-06-20 15:36 ` Eli Zaretskii
2008-06-21 3:40 ` dhruva
2008-06-23 11:01 ` Juanma Barranquero
2008-06-23 18:01 ` Eli Zaretskii
2008-06-20 15:07 ` Eli Zaretskii
2008-06-20 15:19 ` Juanma Barranquero
2008-06-19 19:00 ` Eli Zaretskii
2008-06-17 18:02 ` Stefan Monnier
2008-06-17 17:34 ` Stefan Monnier
2008-06-17 17:45 ` Juanma Barranquero
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=2x3an73lso.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--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 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).