unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: vincent.belaiche@gmail.com (Vincent Belaïche)
Cc: 28601@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.
Date: Mon, 16 Oct 2017 19:19:24 +0300	[thread overview]
Message-ID: <83lgkbf4kz.fsf@gnu.org> (raw)
In-Reply-To: <84h8uzwjqp.fsf@AigleRoyal> (vincent.belaiche@gmail.com)

> From: vincent.belaiche@gmail.com (Vincent Belaïche)
> Cc: Vincent Belaïche <vincent.belaiche@gmail.com> , Glenn
>  Morris <rgm@gnu.org>,
>     Eli Zaretskii <eliz@gnu.org>, 28601@debbugs.gnu.org
> Date: Mon, 16 Oct 2017 10:59:58 +0200
> 
> I attached a patch to INSTALL.W64 to collect all the instruction needed
> in my case to install Emacs.

Thanks, but I wonder how come such a large change is needed for
something that sounds like a simple problem with PATH.  Some of the
changes seem just style or change commands to equivalent ones.

Can you explain what exactly was the problem and how you solved it?
We can then discuss what needs to be changed in the instructions as
written.

Thanks.





      parent reply	other threads:[~2017-10-16 16:19 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
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 [this message]

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=83lgkbf4kz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=28601@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    --cc=vincent.belaiche@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).