unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Fabrice Popineau" <fabrice.popineau@gmail.com>,
	"Francis Wright" <f.j.wright@live.co.uk>,
	"Vincent Belaïche" <vincent.belaiche@gmail.com>,
	28601@debbugs.gnu.org,
	"Stephen Leake" <stephen_leake@stephe-leake.org>,
	"Phillip Lord" <phillip.lord@russet.org.uk>
Subject: bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.
Date: Thu, 16 Nov 2017 09:40:56 -0500	[thread overview]
Message-ID: <CAM-tV-_+uz9JWe1gQGQNqwERZQMXRge4-wMzDC50d20QQGj4pg@mail.gmail.com> (raw)
In-Reply-To: <83vaikr26v.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 25 bytes --]

Here's an updated patch.

[-- Attachment #2: v4-0001-Update-nt-INSTALL.W64-Bug-28601.patch --]
[-- Type: application/octet-stream, Size: 4790 bytes --]

From a4509709fb913999fd469857397c872e45d90751 Mon Sep 17 00:00:00 2001
From: Noam Postavsky <npostavs@gmail.com>
Date: Tue, 7 Nov 2017 18:01:01 -0500
Subject: [PATCH v4] Update nt/INSTALL.W64 (Bug#28601)

* nt/INSTALL.W64 (Download and install MinGW-w64 and MSYS2): Move
suggestion about modifying PATH to...
(Test Emacs): ... here.
(Run configure): Remove the unnecessary setting of PKG_CONFIG_PATH.
(Troubleshooting): New section, includes suggestion to check
PKG_CONFIG_PATH.
---
 nt/INSTALL.W64 | 76 ++++++++++++++++++++++++++++++++++++++++++++--------------
 1 file changed, 58 insertions(+), 18 deletions(-)

diff --git a/nt/INSTALL.W64 b/nt/INSTALL.W64
index 71864ce..e08b72f 100644
--- a/nt/INSTALL.W64
+++ b/nt/INSTALL.W64
@@ -35,18 +35,6 @@ Run this file to install MSYS2 in your preferred directory, e.g. the default
 C:\msys64 -- this will install MinGW-w64 also.  Note that directory names
 containing spaces may cause problems.
 
-Then you'll need to add the following directories to your Windows PATH
-environment variable:
-
-  c:\msys64\usr\bin;c:\msys64\mingw64\bin
-
-you can do this through Control Panel / System and Security / System /
-Advanced system settings / Environment Variables / Edit path.
-
-Adding these directories to your PATH tells Emacs where to find the DLLs it
-needs to run, and some optional commands like grep and find.  These commands
-will also be available at the Windows console.
-
 ** Download and install the necessary packages
 
 Run c:/msys64/msys2.exe in your MSYS2 directory and you will see a BASH window
@@ -112,11 +100,11 @@ C:\emacs\emacs-24.5:
 ** From the Git repository
 
 To download the Git repository, do something like the following -- this will
-put the Emacs source into C:\emacs\emacs-25:
+put the Emacs source into C:\emacs\emacs-26:
 
   mkdir /c/emacs
   cd /c/emacs
-  git clone git://git.sv.gnu.org/emacs.git emacs-25
+  git clone git://git.sv.gnu.org/emacs.git emacs-26
 
 (We recommend using the command shown on Savannah Emacs project page.)
 
@@ -150,11 +138,10 @@ which 'make install' will use - in this example we set it to C:\emacs\emacs-26.
 If a prefix is not specified the files will be put in the standard Unix
 directories located in your C:\msys64 directory, but this is not recommended.
 
-Note also that we need to disable Imagemagick because Emacs does not yet
-support it on Windows.
+Note also that we need to disable Imagemagick and D-Bus because Emacs
+does not yet support them on Windows.
 
-  PKG_CONFIG_PATH=/mingw64/lib/pkgconfig \
-  ./configure --prefix=/c/emacs/emacs-26 --without-imagemagick
+  ./configure --prefix=/c/emacs/emacs-26 --without-imagemagick --without-dbus
 
 ** Run make
 
@@ -192,6 +179,14 @@ To test it out, run
 
 and if all went well, you will have a new 64-bit version of Emacs.
 
+When running Emacs from outside the mingw64 shell, you will need to
+add c:\msys64\mingw64\bin to your Windows PATH, or copy the needed
+DLLs into Emacs' bin/ directory.  Otherwise features such as TLS which
+depend on those DLLs will be missing.
+
+You can do this through Control Panel / System and Security / System /
+Advanced system settings / Environment Variables / Edit path.
+
 * Make a shortcut
 
 To make a shortcut to run the new Emacs, right click on the location where you
@@ -202,6 +197,51 @@ You can set any command line options by right clicking on the resulting
 shortcut, select Properties, then add any options to the Target command,
 e.g. --debug-init.
 
+* Troubleshooting
+
+** Missing mingw64.exe launcher
+
+Older versions of Msys2 may lack the mingw64.exe launcher program.  If
+you have them, running mingw64_shell.bat or "msys2_shell.cmd -mingw64"
+should work instead.
+
+Alternatively, install mingw64.exe with
+
+    pacman -S msys/msys2-launcher-git
+
+** Configure errors
+
+*** Check that mingw64 gcc is accessible
+
+Errors like
+
+    configure: error: Emacs does not support 'x86_64-pc-msys' systems.
+
+or
+
+    checking the compiler's target... configure: error: Impossible to obtain gcc compiler target.
+
+indicate you didn't use the mingw64 launcher, or you didn't install
+gcc.  It's also possible you have something in ~/.bashrc or ~/.profile
+which modifies PATH or MSYSTEM to an unexpected value, preventing gcc
+from being found.  At the mingw64 bash shell, running
+
+    gcc -v
+
+should give output which includes the text
+
+    Target: x86_64-w64-mingw32
+
+*** Check your $PKG_CONFIG_PATH
+
+For a typical MSYS2 install, running
+
+    echo $PKG_CONFIG_PATH
+
+at the mingw64 bash shell should give print a value starting with
+'/mingw64/lib/pkgconfig'.  Incorrect values may prevent configure from
+finding installed libraries.
+
 * Credits
 
 Thanks to Chris Zheng for the original build outline as used by the
-- 
2.6.2.windows.1


  reply	other threads:[~2017-11-16 14:40 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 [this message]
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=CAM-tV-_+uz9JWe1gQGQNqwERZQMXRge4-wMzDC50d20QQGj4pg@mail.gmail.com \
    --to=npostavs@users.sourceforge.net \
    --cc=28601@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=f.j.wright@live.co.uk \
    --cc=fabrice.popineau@gmail.com \
    --cc=phillip.lord@russet.org.uk \
    --cc=stephen_leake@stephe-leake.org \
    --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).