From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: 47120@debbugs.gnu.org
Subject: bug#47120: 28.0.50; [feature/native-comp] Stale *.eln files are not recompiled
Date: Sat, 13 Mar 2021 22:16:42 +0200 [thread overview]
Message-ID: <83tupehkr9.fsf@gnu.org> (raw)
In-Reply-To: <xjftupezubq.fsf@sdf.org> (message from Andrea Corallo on Sat, 13 Mar 2021 20:12:41 +0000)
> From: Andrea Corallo <akrl@sdf.org>
> Cc: 47120@debbugs.gnu.org
> Date: Sat, 13 Mar 2021 20:12:41 +0000
>
> > I'm talking about the *.el files that are not automatically natively
> > compiled, they are natively compiled when first time loaded into
> > Emacs.
>
> I see now thanks, but I'm wondering why should we native compile it
> automatically when the .el is updated later-on if we don't do it during
> the first build?
It just doesn't sound right to me not to update.
But maybe others will think differently.
Or maybe we should by default native-compile all the *.el files in the
tarball as part of the build, and then what I expect will happen
automatically.
next prev parent reply other threads:[~2021-03-13 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 7:58 bug#47120: 28.0.50; [feature/native-comp] Stale *.eln files are not recompiled Eli Zaretskii
2021-03-13 19:43 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-13 19:52 ` Eli Zaretskii
2021-03-13 20:12 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-13 20:16 ` Eli Zaretskii [this message]
2021-03-13 20:26 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-13 20:31 ` Eli Zaretskii
2021-03-13 20:43 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83tupehkr9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=47120@debbugs.gnu.org \
--cc=akrl@sdf.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).