From: Eli Zaretskii <eliz@gnu.org>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: 28601@debbugs.gnu.org
Subject: bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.
Date: Fri, 29 Sep 2017 12:37:30 +0300 [thread overview]
Message-ID: <83r2up976t.fsf@gnu.org> (raw)
In-Reply-To: <vz1shf7dl4u.fsf@gmail.com> (message from Andy Moreton on Thu, 28 Sep 2017 14:10:25 +0100)
> From: Andy Moreton <andrewjmoreton@gmail.com>
> Date: Thu, 28 Sep 2017 14:10:25 +0100
>
> On Wed 27 Sep 2017, Glenn Morris wrote:
>
> > Vincent Belaïche wrote:
> >
> >> There is no such thing as a mingw64_shell.bat script, but there is a
> >> msys2_shell.cmd script, which one can launch with the -mingw64 for
> >> MSYSTEM to be set accordingly to MSYSTEM=MINGW64.
> >
> > Sounds like MinGW has changed how things work and the instructions in
> > nt/INSTALL.W64 need updating.
> >
> >> checking the compiler's target... x86_64-pc-msys
> >> configure: error: Emacs does not support 'x86_64-pc-msys' systems.
> >
> > This is MinGW-specific code added in https://debbugs.gnu.org/19111
>
>
> Newer MSYS2 installations have mingw32.exe, mingw64.exe and msys2.exe for launching a
> shell for each of the build environments, which are more convenient for
> creating desktop shortcuts. Either of the first two can be used to build
> emacs, if the appropriate toolchain is installed.
Can you or someone else suggest a change for INSTALL.W64, if some
change is needed there?
Thanks.
next prev parent reply other threads:[~2017-09-29 9:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 20:02 bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems Vincent Belaïche
2017-09-27 18:36 ` Glenn Morris
2017-09-27 19:07 ` Vincent Belaïche
2017-09-27 19:10 ` Vincent Belaïche
2017-09-27 21:37 ` Glenn Morris
2017-09-28 13:10 ` Andy Moreton
2017-09-29 9:37 ` Eli Zaretskii [this message]
2017-10-12 23:06 ` Noam Postavsky
2017-10-13 6:41 ` Eli Zaretskii
2017-10-13 10:14 ` Andy Moreton
2017-10-13 12:22 ` Eli Zaretskii
2017-10-13 13:52 ` Andy Moreton
2017-10-13 14:38 ` Eli Zaretskii
2017-10-13 16:33 ` Noam Postavsky
2017-10-13 17:24 ` Eli Zaretskii
2017-10-13 17:51 ` Noam Postavsky
2017-10-13 18:35 ` Eli Zaretskii
2017-10-13 14:09 ` Vincent Belaïche
2017-10-13 14:16 ` Noam Postavsky
2017-10-14 1:40 ` Noam Postavsky
2017-10-16 8:59 ` Vincent Belaïche
2017-10-16 14:23 ` Noam Postavsky
2017-10-16 17:11 ` Vincent Belaïche
2017-10-16 21:42 ` Noam Postavsky
2017-10-19 8:25 ` Vincent Belaïche
2017-11-08 2:37 ` Noam Postavsky
2017-11-08 16:05 ` Eli Zaretskii
2017-11-08 17:42 ` Noam Postavsky
2017-11-08 18:13 ` Eli Zaretskii
2017-11-08 19:23 ` Noam Postavsky
2017-11-08 19:38 ` Eli Zaretskii
2017-11-16 14:40 ` Noam Postavsky
2017-11-16 16:11 ` Eli Zaretskii
2017-11-21 19:44 ` Noam Postavsky
2017-10-16 16:19 ` 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=83r2up976t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28601@debbugs.gnu.org \
--cc=andrewjmoreton@gmail.com \
/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).