From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: corwin@bru.st, 58318@debbugs.gnu.org, bartosz.bubak@gmail.com,
Andrea Corallo <akrl@sdf.org>
Subject: bug#58318: 28.2; Emacs installed from package won't work with MinGW
Date: Fri, 07 Oct 2022 14:04:57 +0200 [thread overview]
Message-ID: <87sfjzvnyu.fsf@gnus.org> (raw)
In-Reply-To: <83edvjondh.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 07 Oct 2022 14:59:38 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> I'm sorry, I don't follow you. If trampolines can't be installed, then
>> Emacs isn't fully functional, because you can't say
>>
>> (fset 'yes-or-no-p 'y-or-n-p)
>>
>> and have that be respected. I.e., the non-functional bit is about
>> redefinitions of built-in functions, which is pretty basic functionality
>> in Emacs.
>
> Maybe there's a misunderstanding of what you meant by "if a compiler
> isn't present". By "the compiler" do you mean libgccjit, or is it GCC
> and Binutils (or maybe all 3 together)? IOW, are you talking about
> the ability to load existing *.eln files, or are you talking about the
> ability to both load existing *.eln files and produce new ones?
I'm talking about trampolines, nothing else.
> The startup code currently detects that libgccjit is unavailable or
> cannot be loaded, and if so, disables all the aspects of
> native-compilation: both JIT compilation of *.el and production of the
> trampolines. I'm not aware that when we disable those two, we get
> Emacs that is not "fully functional".
If native compilation is disabled in a native-compiled Emacs, then
(fset 'yes-or-no-p 'y-or-n-p)
doesn't work (for calls to `yes-or-no-p' in native-compiled code).
That's what I meant by "not fully functional".
next prev parent reply other threads:[~2022-10-07 12:04 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 16:01 bug#58318: 28.2; Emacs installed from package won't work with MinGW Bartosz Bubak
2022-10-06 5:44 ` Eli Zaretskii
2022-10-06 13:09 ` Corwin Brust
2022-10-06 13:30 ` Lars Ingebrigtsen
2022-10-06 14:43 ` Eli Zaretskii
2022-10-07 11:42 ` Lars Ingebrigtsen
2022-10-07 11:59 ` Eli Zaretskii
2022-10-07 12:04 ` Lars Ingebrigtsen [this message]
2022-10-07 12:12 ` Eli Zaretskii
2022-10-07 12:28 ` Lars Ingebrigtsen
2022-10-07 12:35 ` Andrea Corallo
2022-10-07 12:43 ` Lars Ingebrigtsen
2022-10-07 12:54 ` Eli Zaretskii
2022-10-07 13:02 ` Lars Ingebrigtsen
2022-10-07 13:44 ` Eli Zaretskii
2022-10-07 13:47 ` Lars Ingebrigtsen
2022-10-07 13:04 ` Andrea Corallo
2022-10-07 13:48 ` Eli Zaretskii
2022-10-07 13:54 ` Andrea Corallo
2022-10-07 14:03 ` Eli Zaretskii
2022-10-07 14:35 ` Andrea Corallo
2022-10-07 15:27 ` Eli Zaretskii
2022-10-07 15:34 ` Corwin Brust
2022-10-07 15:43 ` Eli Zaretskii
2022-10-07 15:47 ` Corwin Brust
2022-10-07 19:11 ` Eli Zaretskii
2022-10-07 17:15 ` Andrea Corallo
2022-10-07 19:15 ` Eli Zaretskii
2022-10-07 15:49 ` Andrea Corallo
2022-10-07 15:52 ` Corwin Brust
2022-10-07 19:14 ` Eli Zaretskii
2022-10-08 12:56 ` Lars Ingebrigtsen
2022-10-08 13:03 ` Eli Zaretskii
2022-10-08 13:10 ` Lars Ingebrigtsen
2022-10-08 14:28 ` Eli Zaretskii
2022-10-08 13:28 ` Andrea Corallo
2022-10-11 19:23 ` Andrea Corallo
2022-10-11 19:29 ` Eli Zaretskii
2022-10-11 20:45 ` Andrea Corallo
2022-10-12 5:21 ` Eli Zaretskii
2022-10-12 8:14 ` Andrea Corallo
2022-10-12 12:50 ` Eli Zaretskii
2022-10-12 14:55 ` Andrea Corallo
2022-10-12 15:35 ` Eli Zaretskii
2022-10-13 13:26 ` Andrea Corallo
2022-10-06 14:41 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfjzvnyu.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=58318@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=bartosz.bubak@gmail.com \
--cc=corwin@bru.st \
--cc=eliz@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.
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.