From: Arash Esbati <arash@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 53497@debbugs.gnu.org
Subject: bug#53497: 29.0.50; native-compile after restarting Emacs
Date: Mon, 24 Jan 2022 13:50:19 +0100 [thread overview]
Message-ID: <864k5tz4ac.fsf@gnu.org> (raw)
In-Reply-To: <83zgnljop0.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 24 Jan 2022 14:36:11 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Arash Esbati <arash@gnu.org>
>> Date: Mon, 24 Jan 2022 11:35:38 +0100
>> Cc: 53497@debbugs.gnu.org
>>
>> >> Am I missing something? This is Emacs dee029e19f compiled on Win10.
>
> How did you compile Emacs? did you use NATIVE_FULL_AOT=1 to natively
> compile all the bundled *.el files, or did you use the default build
> procedure that only natively compile only the preloaded *.el files?
I only pass '--with-native-compilation' to configure.
>> Sorry if I wasn't clear. In case 2, Gnus libraries are not compiled at
>> all and I stick with 77 .eln files. In case 1, I go up to more than 100
>> .eln files.
>
> If Emacs doesn't natively compile files it loads, it generally means
> it cannot access the source *.el files, or that you load the *.el
> files explicitly with the .el extension.
>
> And I don't understand why the Gnus files need to be compiled each
> time in the first place.
That's not my issue. I don't want the files to be compiled again and
again (see below).
> they aren't supposed to change, so they should be natively compiled
> just once, when you first load them into an Emacs session.
This is exactly my problem that files don't get compiled if I re-start
Emacs and then they are loaded (e.g. RefTeX). It works only in the
first session when Emacs sees the empty ~/.emacs.d/eln-cache/ and starts
the machinery.
Best, Arash
next prev parent reply other threads:[~2022-01-24 12:50 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 10:20 bug#53497: 29.0.50; native-compile after restarting Emacs Arash Esbati
2022-01-24 10:30 ` Lars Ingebrigtsen
2022-01-24 10:35 ` Arash Esbati
2022-01-24 10:40 ` Lars Ingebrigtsen
2022-01-24 11:00 ` Arash Esbati
2022-01-24 12:28 ` Eli Zaretskii
2022-01-24 12:43 ` Arash Esbati
2022-01-24 12:36 ` Eli Zaretskii
2022-01-24 12:50 ` Arash Esbati [this message]
2022-01-24 12:56 ` Eli Zaretskii
2022-01-24 13:33 ` Arash Esbati
2022-01-24 13:45 ` Eli Zaretskii
2022-01-24 13:50 ` Eli Zaretskii
2022-01-24 14:27 ` Andrea Corallo
2022-01-24 14:31 ` Eli Zaretskii
2022-01-24 17:17 ` Arash Esbati
2022-01-24 19:08 ` Eli Zaretskii
2022-01-25 11:01 ` Arash Esbati
2022-01-25 12:36 ` Eli Zaretskii
2022-01-25 12:49 ` Arash Esbati
2022-01-25 13:31 ` Eli Zaretskii
2022-01-26 11:25 ` Arash Esbati
2022-01-26 13:22 ` Eli Zaretskii
2022-01-26 14:58 ` Arash Esbati
2022-01-26 15:13 ` Eli Zaretskii
2022-01-26 15:20 ` Arash Esbati
2022-01-26 16:54 ` Eli Zaretskii
2022-01-26 19:06 ` Arash Esbati
2022-01-26 19:30 ` Eli Zaretskii
2022-01-26 15:58 ` Andrea Corallo
2022-01-27 10:11 ` Andrea Corallo
2022-01-27 10:31 ` Eli Zaretskii
2022-01-27 10:57 ` Andrea Corallo
2022-01-27 11:03 ` Eli Zaretskii
2022-01-27 12:58 ` Andrea Corallo
2022-01-27 15:03 ` Arash Esbati
2022-01-27 15:22 ` Eli Zaretskii
2022-01-27 16:27 ` Arash Esbati
2022-01-27 16:37 ` Andrea Corallo
2022-01-27 16:57 ` Eli Zaretskii
2022-01-27 17:22 ` Andrea Corallo
2022-01-27 22:21 ` Andrea Corallo
2022-01-28 9:24 ` Arash Esbati
2022-01-28 12:15 ` Eli Zaretskii
2022-01-28 15:12 ` Andrea Corallo
2022-01-28 16:02 ` Andrea Corallo
2022-01-28 16:30 ` Lars Ingebrigtsen
2022-01-29 7:40 ` Andrea Corallo
2022-01-29 10:02 ` Eli Zaretskii
2022-01-29 11:49 ` Arash Esbati
2022-01-27 16:58 ` Arash Esbati
2022-01-27 17:03 ` Eli Zaretskii
2022-01-28 9:26 ` Arash Esbati
2022-01-24 16:33 ` Arash Esbati
2022-01-24 17:07 ` Eli Zaretskii
2022-01-24 18:47 ` Arash Esbati
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=864k5tz4ac.fsf@gnu.org \
--to=arash@gnu.org \
--cc=53497@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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.