From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: why are files like tramp-loaddefs.el and cl-loaddefs.el natively compiled on each startup?
Date: Mon, 09 Jan 2023 20:45:17 +0200 [thread overview]
Message-ID: <83v8lfo8ci.fsf@gnu.org> (raw)
In-Reply-To: <87358job2a.fsf@metapensiero.it> (message from Lele Gaifax on Mon, 09 Jan 2023 18:46:37 +0100)
> From: Lele Gaifax <lele@metapensiero.it>
> Date: Mon, 09 Jan 2023 18:46:37 +0100
>
> Emanuel Berg <incal@dataswamp.org> writes:
>
> > Why are files like tramp-loaddefs.el and cl-loaddefs.el
> > natively compiled on each startup?
> >
> > They change all the time?
> >
> > Why?
>
> I'm experiencing the same thing, in several different "setups"
> (doom-emacs and my own home-made configuration), with both GNU/Emacs 29
> and master: every time I launch a new Emacs, I see the following in the
> *Async-native-compile-log* buffer:
>
> Compiling /usr/local/share/emacs/30.0.50/lisp/net/tramp-loaddefs.el.gz...
> uncompressing tramp-loaddefs.el.gz...
> uncompressing tramp-loaddefs.el.gz...done
> Compiling /usr/local/share/emacs/30.0.50/lisp/emacs-lisp/cl-loaddefs.el.gz...
> uncompressing cl-loaddefs.el.gz...
> uncompressing cl-loaddefs.el.gz...done
> Compilation finished.
> Compilation finished.
They are marked with no-native-compile:t, so Emacs isn't actually
compiling them.
FWIW, I don't see those messages when I start Emacs.
next prev parent reply other threads:[~2023-01-09 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 6:53 why are files like tramp-loaddefs.el and cl-loaddefs.el natively compiled on each startup? Emanuel Berg
2023-01-09 17:46 ` Lele Gaifax
2023-01-09 18:45 ` Eli Zaretskii [this message]
2023-01-09 19:25 ` Emanuel Berg
2023-01-09 20:23 ` 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=83v8lfo8ci.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).