From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Eli Zaretskii <eliz@gnu.org>
Cc: helohe@bluewin.ch, emacs-devel@gnu.org
Subject: Re: MinGW build on master fails with Error 127
Date: Sat, 24 Dec 2022 17:14:56 +0100 [thread overview]
Message-ID: <87o7rs22yn.fsf@telefonica.net> (raw)
In-Reply-To: <83y1qw4x8w.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 24 Dec 2022 17:50:07 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Please note that MinGW-w64 and MSYS2 (which includes MINGW-packages) are
>> different projects. MSYS2 builds, packages and distributes MinGW-w64.
>> MSYS2 decided to bump _WIN32_WINNT in our build scripts, which has
>> implications for Emacs (see below) but that's independent of what
>> MinGW-w64 actually, officially supports.
>
> So what are the details? Which versions of Windows does MSYS2
> support,
Since about 1 week ago, the minimum requirement is Windows 8.1. Hardware
requirements were also recently upgraded. A CPU from 2007 onwards should
be fine:
https://www.msys2.org/news/#2022-10-18-new-minimum-hardware-requirements-cpus-from-20067
> and which ones does MinGW64 support?
AFAIK nothing changed for MinGW-w64. I don't know about their planning,
though.
> And if MinGW64 is about
> to drop Windows versions older than 8.1 soon, when will that happen?
See above. Please note that Mingw-w64 alone is useless, you need to
configure your toolchain to use it. MSYS2 provides toolchains ready to
use. Plus, requirements such as libwinpthreads, which are also
maintained by Mingw-w64, might have their own requirements (AFAIK
nothing changed yet.)
> I'm asking because I want to update our documentation with this
> information, to avoid other users being surprised by these subtle
> issues.
I would say that for using an MSYS2-based build of Emacs you need
Windows 8.1 at the least. A more future-proof statement is to recommend
looking up that information on the MSYS2 web page.
next prev parent reply other threads:[~2022-12-24 16:14 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 15:26 MinGW build on master fails with Error 127 Loreno Heer
2022-12-12 15:40 ` Eli Zaretskii
2022-12-12 15:44 ` Loreno Heer
2022-12-12 15:56 ` Eli Zaretskii
2022-12-12 16:03 ` Loreno Heer
2022-12-12 16:11 ` Eli Zaretskii
2022-12-12 16:54 ` Loreno Heer
2022-12-23 21:45 ` Loreno Heer
2022-12-24 6:36 ` Eli Zaretskii
2022-12-24 14:18 ` Loreno Heer
2022-12-24 14:43 ` Eli Zaretskii
2022-12-24 15:11 ` Loreno Heer
2022-12-24 15:44 ` Eli Zaretskii
2022-12-24 22:50 ` Loreno Heer
2022-12-24 15:31 ` Óscar Fuentes
2022-12-24 15:50 ` Eli Zaretskii
2022-12-24 16:14 ` Óscar Fuentes [this message]
2022-12-24 16:46 ` Eli Zaretskii
2022-12-24 16:58 ` Óscar Fuentes
2022-12-24 17:08 ` Óscar Fuentes
2022-12-24 17:20 ` Eli Zaretskii
2022-12-24 17:57 ` Óscar Fuentes
2022-12-24 18:09 ` Eli Zaretskii
2022-12-24 18:56 ` Óscar Fuentes
2022-12-24 19:10 ` Eli Zaretskii
2022-12-25 2:46 ` Óscar Fuentes
2022-12-25 8:29 ` Eli Zaretskii
2022-12-25 14:25 ` Óscar Fuentes
2022-12-26 13:02 ` Eli Zaretskii
2022-12-26 13:33 ` Óscar Fuentes
2022-12-24 19:19 ` Óscar Fuentes
2022-12-24 19:27 ` Eli Zaretskii
2022-12-25 0:13 ` Po Lu
2022-12-25 0:48 ` Óscar Fuentes
2022-12-25 6:46 ` Eli Zaretskii
2022-12-24 18:03 ` Óscar Fuentes
2022-12-24 18:49 ` Eli Zaretskii
2022-12-24 19:23 ` Óscar Fuentes
2022-12-24 19:29 ` Eli Zaretskii
2022-12-24 19:44 ` Óscar Fuentes
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=87o7rs22yn.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=helohe@bluewin.ch \
/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.