From: Andrea Corallo <akrl@sdf.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, Corwin Brust <corwin@bru.st>,
58318@debbugs.gnu.org, bartosz.bubak@gmail.com
Subject: bug#58318: 28.2; Emacs installed from package won't work with MinGW
Date: Fri, 07 Oct 2022 17:15:36 +0000 [thread overview]
Message-ID: <xjftu4f1rnr.fsf@ma.sdf.org> (raw)
In-Reply-To: <83h70fmyg7.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 07 Oct 2022 18:43:20 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Corwin Brust <corwin@bru.st>
>> Date: Fri, 7 Oct 2022 10:34:38 -0500
>> Cc: Andrea Corallo <akrl@sdf.org>, larsi@gnus.org, bartosz.bubak@gmail.com,
>> 58318@debbugs.gnu.org
>>
>> FWIW, It appeared to take around 12 minutes to build all trampolines
>> starting from the "installed" Emacs that was the source for the 28.2
>> binary zips.
>
> Is that serially, i.e. using a single Emacs process at a time?
The other (last?) option is to have one single .eln containing all
trampolines. It should be very quick to compile, the downside is some
more memory usage (we'd have to load and map this .eln when the first
trampoline is requested).
Andrea
next prev parent reply other threads:[~2022-10-07 17:15 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 [this message]
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
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=xjftu4f1rnr.fsf@ma.sdf.org \
--to=akrl@sdf.org \
--cc=58318@debbugs.gnu.org \
--cc=bartosz.bubak@gmail.com \
--cc=corwin@bru.st \
--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 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).