nt/INSTALL: Add note about problematic characters passed to configure.

diff --git a/nt/ChangeLog b/nt/ChangeLog
index 5dff8b27737ba348202eddc4c7d1c9894f02f3ca..5f92bedd8c19f3e091932c172945fb2a12a79261 100644 (file)
--- a/nt/ChangeLog
+++ b/nt/ChangeLog
@@ -1,3 +1,7 @@
+2010-10-06  Juanma Barranquero  <lekktu@gmail.com>
+
+       * INSTALL: Add note about problematic characters passed to configure.
+
 2010-10-01  Eli Zaretskii  <eliz@gnu.org>
 
        * makefile.w32-in (frc, TAGS, TAGS-gmake, TAGS-nmake): New targets.

diff --git a/nt/INSTALL b/nt/INSTALL
index 8af8e3020decd0744483708d55c141fe86566779..c26ab196bd2acd3e2fb2d4436323a5414c6ffcf4 100644 (file)
--- a/nt/INSTALL
+++ b/nt/INSTALL
@@ -221,6 +221,14 @@
   absolutely sure the produced binaries will never need to be run under
   a debugger.
 
+  Because of limitations of the stock Windows command shell, certain
+  characters (quotes, backslashes and equal signs) can be problematic
+  and should not be used in arguments to configure.  That means that
+  forward slashes must be used in paths passed to the compiler and
+  linker via the --cflags and --ldflags options, and that it is
+  currently not possible to pass a macro like -DFOO=BAR (though -DFOO
+  is perfectly valid).
+
   N.B.  It is normal to see a few error messages output while configure
   is running, when gcc support is being tested.  These cannot be
   suppressed because of limitations in the Windows 9X command.com shell.