all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Loreno Heer <helohe@bluewin.ch>
Cc: emacs-devel@gnu.org
Subject: Re: MinGW build on master fails with Error 127
Date: Sat, 24 Dec 2022 16:43:00 +0200	[thread overview]
Message-ID: <835ye06ex7.fsf@gnu.org> (raw)
In-Reply-To: <832966a5-bd27-76f9-4757-a8c246eca416@bluewin.ch> (message from Loreno Heer on Sat, 24 Dec 2022 15:18:02 +0100)

> Date: Sat, 24 Dec 2022 15:18:02 +0100
> Cc: emacs-devel@gnu.org
> From: Loreno Heer <helohe@bluewin.ch>
> 
> I did and if I understand it correctly they basically say that they did
> some change but it is now up to emacs to change the build behavior:
> 
> https://github.com/msys2/MINGW-packages/issues/14573#issuecomment-1364532147

Are you building Emacs on Windows 7?  If yes, I understand what they
are saying: that MinGW64 no longer supports Windows 7.

If you build on a later version of Windows, then I don't understand
what they are saying:

  As examples mentioned on #14452 illustrate, a package can support
  Win7 fine but if we say to its build system that we target >Win7 the
  resulting binary may be incompatible with Win7. This means in
  practice that Emacs (or any other software) can't rely on using our
  packages as runtime dependencies for supporting Win7.

Emacs will support MS-Windows versions as old as Windows 9X, as long
as the MinGW headers and runtime support those versions.  If your
MinGW supports only Windows versions newer than some version N, then
Emacs cannot magically overcome this limitation, and will also support
only versions of Windows newer than N.



  reply	other threads:[~2022-12-24 14:43 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 [this message]
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
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=835ye06ex7.fsf@gnu.org \
    --to=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.