From: Eli Zaretskii <eliz@gnu.org>
To: Corwin Brust <corwin@bru.st>
Cc: 58318@debbugs.gnu.org, bartosz.bubak@gmail.com
Subject: bug#58318: 28.2; Emacs installed from package won't work with MinGW
Date: Thu, 06 Oct 2022 17:41:27 +0300 [thread overview]
Message-ID: <83leptovzc.fsf@gnu.org> (raw)
In-Reply-To: <CAJf-WoRbE4BknoYRv-0fxmF8N7DQzZuEV869bXNRjc374anp3w@mail.gmail.com> (message from Corwin Brust on Thu, 6 Oct 2022 08:09:16 -0500)
> From: Corwin Brust <corwin@bru.st>
> Date: Thu, 6 Oct 2022 08:09:16 -0500
> Cc: Bartosz Bubak <bartosz.bubak@gmail.com>, 58318@debbugs.gnu.org
>
> If, per the configuration reported when generating this bug report,
> Emacs can see libgccjit is not available, then should Emacs still be
> trying to native compile org-entitles in this case?
No, it should disable that in startup.el:
(when (featurep 'native-compile)
(unless (native-comp-available-p)
;; Disable deferred async compilation and trampoline synthesis
;; in this session. This is necessary if libgccjit is not
;; available on MS-Windows, but Emacs was built with
;; native-compilation support.
(setq native-comp-deferred-compilation nil
comp-enable-subr-trampolines nil))
But libgccjit DLL _is_ available in this case, so maybe the test
doesn't discover the problem.
prev parent reply other threads:[~2022-10-06 14:41 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
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 [this message]
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=83leptovzc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58318@debbugs.gnu.org \
--cc=bartosz.bubak@gmail.com \
--cc=corwin@bru.st \
/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).