From: Lars Ingebrigtsen <larsi@gnus.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: Max Brieiev <max.brieiev@gmail.com>, 58429@debbugs.gnu.org
Subject: bug#58429: 29.0.50; inhibit-automatic-native-compilation does not work as expected.
Date: Tue, 11 Oct 2022 21:41:37 +0200 [thread overview]
Message-ID: <87ilkqf8r2.fsf@gnus.org> (raw)
In-Reply-To: <xjfa662179z.fsf@ma.sdf.org> (Andrea Corallo's message of "Tue, 11 Oct 2022 19:37:12 +0000")
Andrea Corallo <akrl@sdf.org> writes:
> Exactly. I don't think magit is trying to invoke the native compiler
> directly (I don't see any trace of that in magit's source code). Also
> other packages are reported to show the same issue (probably the one
> with no .eln already available).
>
> If this is the case is just `inhibit-automatic-native-compilation' not
> doing what it promises (read being broken).
It's meant to inhibit JIT compilation:
"If non-nil, inhibit automatic native compilation of loaded .elc files."
package.el calls the native-compilation functions directly, and are not
affected by the variable at all (as currently designed).
next prev parent reply other threads:[~2022-10-11 19:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 7:21 bug#58429: 29.0.50; inhibit-automatic-native-compilation does not work as expected Max Brieiev
2022-10-11 8:11 ` Lars Ingebrigtsen
2022-10-11 9:19 ` Max Brieiev
2022-10-11 19:37 ` Andrea Corallo
2022-10-11 19:41 ` Lars Ingebrigtsen [this message]
2022-10-11 20:49 ` Andrea Corallo
2022-10-12 10:57 ` Lars Ingebrigtsen
2022-10-12 11:15 ` Max Brieiev
2022-10-12 11:30 ` Lars Ingebrigtsen
2022-10-12 11:57 ` Max Brieiev
2022-10-12 12:59 ` Lars Ingebrigtsen
2022-10-12 13:31 ` Eli Zaretskii
2022-10-12 14:11 ` Max Brieiev
2022-10-12 15:32 ` Eli Zaretskii
2022-10-12 16:54 ` Max Brieiev
2022-10-12 17:07 ` Eli Zaretskii
2022-10-13 14:10 ` Andrea Corallo
2022-10-13 16:05 ` Eli Zaretskii
2022-10-14 20:10 ` Andrea Corallo
2022-10-15 9:17 ` Eli Zaretskii
2022-10-15 16:01 ` Andrea Corallo
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=87ilkqf8r2.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=58429@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=max.brieiev@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 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.