summaryrefslogtreecommitdiff
path: root/nt
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2006-10-08 04:32:28 +0000
committerEli Zaretskii <eliz@gnu.org>2006-10-08 04:32:28 +0000
commit117dde84668f90a0549adb898babd270b633f798 (patch)
tree173dae4e6e83d47c59a40a1e16848454d6b981c7 /nt
parent3ebde3fb70b816db009cd1ca738c88089f9f8cc9 (diff)
downloademacs-117dde84668f90a0549adb898babd270b633f798.tar.gz
Add compatibility data for Cygwin Make 3.81.
Diffstat (limited to 'nt')
-rw-r--r--nt/INSTALL4
1 files changed, 3 insertions, 1 deletions
diff --git a/nt/INSTALL b/nt/INSTALL
index 21ee8367a88..8415b1893ff 100644
--- a/nt/INSTALL
+++ b/nt/INSTALL
@@ -103,7 +103,7 @@
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
+ or sh.exe., a port of a Unixy shell. For reference, below 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
@@ -129,6 +129,8 @@
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]
+ cygwin compiled make 3.80: fails?[6] fails?[6]
+ cygwin compiled make 3.81: fails fails?[6]
mingw32 compiled make 3.79.1: okay okay
mingw32 compiled make 3.80: okay unknown[6]
mingw32 compiled make 3.81: okay okay[7]