Mercurial > emacs

changeset 67016:47fccd30153d

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Rearrange text to make it clear that the make/shell compatibility table refers only to the MinGW build.
author Eli Zaretskii <eliz@gnu.org>
date Sat, 19 Nov 2005 13:19:58 +0000
parents 21e2e3358403
children fb42f801f872
files nt/INSTALL
diffstat 1 files changed, 45 insertions(+), 41 deletions(-) [+]
line wrap: on
line diff
--- a/nt/INSTALL	Sat Nov 19 13:12:05 2005 +0000
+++ b/nt/INSTALL	Sat Nov 19 13:19:58 2005 +0000
@@ -29,11 +29,55 @@
 
   To compile Emacs, you will need either Microsoft Visual C++ 2.0 or
   later and nmake, or a Windows port of GCC 2.95 or later with MinGW
-  and W32 API support and a port of GNU make.  You can use the Cygwin
+  and W32 API support and a port of GNU Make.  You can use the Cygwin
   ports of GCC, but Emacs requires the MinGW headers and libraries to
   build (latest versions of the Cygwin toolkit, at least since v1.3.3,
   include the MinGW headers and libraries as an integral part).
 
+  If you use the MinGW port of GCC and GNU Make to build Emacs, there
+  are some compatibility issues wrt Make and the shell that is run by
+  Make, either the standard COMMAND.COM/CMD.EXE supplied with Windows
+  or sh.exe., a port of a Unixy shell.  For reference, here is a list
+  of which builds of GNU Make are known to work or not, and whether
+  they work in the presence and/or absence of sh.exe, the Cygwin port
+  of Bash. Note that any version of Make that is compiled with Cygwin
+  will only work with Cygwin tools, due to the use of cygwin style
+  paths.  This means Cygwin Make is unsuitable for building parts of
+  Emacs that need to invoke Emacs itself (leim and "make bootstrap",
+  for example).  Also see the Trouble-shooting section below if you
+  decide to go ahead and use Cygwin make.
+
+  In addition, using 4NT as your shell is known to fail the build process,
+  at least for 4NT version 3.01.  Use CMD.EXE, the default Windows shell,
+  instead. MSYS sh.exe also appears to cause various problems. If you have
+  MSYS installed, try "make SHELL=cmd.exe" to force the use of cmd.exe
+  instead of sh.exe.
+
+                                         sh exists     no sh
+
+    cygwin b20.1 make (3.75):            fails[1, 5]   fails[2, 5]
+    MSVC compiled gmake 3.77:            okay          okay
+    MSVC compiled gmake 3.78.1:          okay          okay
+    MSVC compiled gmake 3.79.1:          okay          okay
+    mingw32/gcc-2.92.2 make (3.77):      okay          okay[4]
+    cygwin compiled gmake 3.77:          fails[1, 5]   fails[2, 5]
+    cygwin compiled make 3.78.1:         fails[5]      fails[2, 5]
+    cygwin compiled make 3.79.1:         fails[3, 5]   fails[2?, 5]
+    mingw32 compiled make 3.79.1:        okay          okay
+    mingw32 compiled make 3.80:          okay          unknown[6]
+
+  Notes:
+
+    [1] doesn't cope with makefiles with DOS line endings, so must mount
+        emacs source with text!=binary.
+    [2] fails when needs to invoke shell commands; okay invoking gcc etc.
+    [3] requires LC_MESSAGES support to build; cannot build with early
+        versions of cygwin.
+    [4] may fail on Windows 9X and Windows ME; if so, install Bash.
+    [5] fails when building leim due to the use of cygwin style paths.
+        May work if building emacs without leim.
+    [6] please report if you try this combination.
+
   Other compilers may work, but specific reports from people that have
   tried suggest that the Intel C compiler (for example) may produce an
   Emacs executable with strange filename completion behaviour.  Unless
@@ -62,46 +106,6 @@
 
   http://ourcomments.org/Emacs/w32-build-emacs.html
 
-  For reference, here is a list of which builds of GNU make are known
-  to work or not, and whether they work in the presence and/or absence
-  of sh.exe, the Cygwin port of Bash. Note that any version of make
-  that is compiled with Cygwin will only work with Cygwin tools, due to
-  the use of cygwin style paths. This means Cygwin make is unsuitable
-  for building parts of Emacs that need to invoke Emacs itself (leim and
-  "make bootstrap", for example). Also see the Trouble-shooting section
-  below if you decide to go ahead and use Cygwin make.
-
-  In addition, using 4NT as your shell is known to fail the build process,
-  at least for 4NT version 3.01.  Use cmd.exe, the default NT shell,
-  instead. MSYS sh.exe also appears to cause various problems. If you have
-  MSYS installed, try "make SHELL=cmd.exe" to force the use of cmd.exe
-  instead of sh.exe.
-
-                                         sh exists     no sh
-
-    cygwin b20.1 make (3.75):            fails[1, 5]   fails[2, 5]
-    MSVC compiled gmake 3.77:            okay          okay
-    MSVC compiled gmake 3.78.1:          okay          okay
-    MSVC compiled gmake 3.79.1:          okay          okay
-    mingw32/gcc-2.92.2 make (3.77):      okay          okay[4]
-    cygwin compiled gmake 3.77:          fails[1, 5]   fails[2, 5]
-    cygwin compiled make 3.78.1:         fails[5]      fails[2, 5]
-    cygwin compiled make 3.79.1:         fails[3, 5]   fails[2?, 5]
-    mingw32 compiled make 3.79.1:        okay          okay
-    mingw32 compiled make 3.80:          okay          unknown[6]
-
-  Notes:
-
-    [1] doesn't cope with makefiles with DOS line endings, so must mount
-        emacs source with text!=binary.
-    [2] fails when needs to invoke shell commands; okay invoking gcc etc.
-    [3] requires LC_MESSAGES support to build; cannot build with early
-        versions of cygwin.
-    [4] may fail on Windows 9X and Windows ME; if so, install Bash.
-    [5] fails when building leim due to the use of cygwin style paths.
-        May work if building emacs without leim.
-    [6] please report if you try this combination.
-
 * Configuring
 
   Configuration of Emacs is now handled by running configure.bat in the