From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: larsi@gnus.org, corwin@bru.st, bartosz.bubak@gmail.com,
58318@debbugs.gnu.org
Subject: bug#58318: 28.2; Emacs installed from package won't work with MinGW
Date: Wed, 12 Oct 2022 18:35:20 +0300 [thread overview]
Message-ID: <83pmexawcn.fsf@gnu.org> (raw)
In-Reply-To: <xjfilkpytuj.fsf@ma.sdf.org> (message from Andrea Corallo on Wed, 12 Oct 2022 14:55:32 +0000)
> From: Andrea Corallo <akrl@sdf.org>
> Cc: larsi@gnus.org, corwin@bru.st, 58318@debbugs.gnu.org,
> bartosz.bubak@gmail.com
> Date: Wed, 12 Oct 2022 14:55:32 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Andrea Corallo <akrl@sdf.org>
> >> Cc: larsi@gnus.org, corwin@bru.st, 58318@debbugs.gnu.org,
> >> bartosz.bubak@gmail.com
> >> Date: Wed, 12 Oct 2022 08:14:43 +0000
> >>
> >> Eli Zaretskii <eliz@gnu.org> writes:
> >>
> >> >> make bootstrap on my dev machine (-j16) is ~ 3min 10 secs.
> >> >
> >> > I meant the time to build a release tarball, which should be much
> >> > shorter. Sorry for being unclear.
> >>
> >> Apologies on my side, I'm not very much into release tarball generation.
> >> If you specify what's the command you are referring to I can time it and
> >> report.
> >
> > It isn't too important, so feel free to disregard. But if you have a
> > few minutes, then unpack the Emacs 28.2 release tarball and build it
> > with -j16.
>
> Ok,
>
> on my machine is about 40secs the configure phase and ~1min make -j16.
Thanks, that confirms previous findings: compiling all the trampolines
takes roughly the same time as building the tarball.
next prev parent reply other threads:[~2022-10-12 15:35 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 [this message]
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=83pmexawcn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58318@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=bartosz.bubak@gmail.com \
--cc=corwin@bru.st \
--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.