From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 57152@debbugs.gnu.org
Subject: bug#57152: 29.0.50; Emacs executable isn't rebuilt when loaddefs.el is modified
Date: Wed, 17 Aug 2022 12:40:32 +0200 [thread overview]
Message-ID: <877d37kva7.fsf@gnus.org> (raw)
In-Reply-To: <m2bksliqdg.fsf@Mini.fritz.box> ("Gerd Möllmann"'s message of "Mon, 15 Aug 2022 15:32:43 +0200")
Gerd Möllmann <gerd.moellmann@gmail.com> writes:
> Could it be that src/Makefile is simply not invoked after lisp/Makefile
> has built loaddefs.*? In Makefile.in we have
>
> SUBDIR = $(NTDIR) lib lib-src src lisp
> ...
> all: ${SUBDIR} info $(gsettings_SCHEMAS:.xml=.valid)
>
> That is src comes before lisp. Haching something like a second 'make
> -C' at the end seems to do something not entirely unreasonable.
Hm, interesting... but I think we might end up in a situation where we
first build the Emacs executable, then update the loaddefs.el, and then
build the Emacs executable again.
But perhaps that's OK -- while we're scanning for new loaddefs every
build, there's seldom any new ;;;###autoloads, so the loaddefs.el file
doesn't update all that often.
I'm not quite sure where the second "make -C" would go, though.
next prev parent reply other threads:[~2022-08-17 10:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 7:03 bug#57152: 29.0.50; Emacs executable isn't rebuilt when loaddefs.el is modified Eli Zaretskii
2022-08-12 15:14 ` Lars Ingebrigtsen
2022-08-12 15:29 ` Eli Zaretskii
2022-08-13 11:42 ` Lars Ingebrigtsen
2022-08-15 10:07 ` Lars Ingebrigtsen
2022-08-15 11:58 ` Eli Zaretskii
2022-08-15 13:32 ` Gerd Möllmann
2022-08-17 10:40 ` Lars Ingebrigtsen [this message]
2022-08-17 13:50 ` Gerd Möllmann
2022-08-18 12:46 ` Lars Ingebrigtsen
2022-08-19 9:24 ` Gerd Möllmann
2022-08-17 10:34 ` Lars Ingebrigtsen
2022-08-17 12:08 ` 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
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=877d37kva7.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=57152@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@gmail.com \
/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).