From 6072fed48b8d5282530a0c3fe1c977d80e925488 Mon Sep 17 00:00:00 2001 From: Juanma Barranquero Date: Wed, 6 Oct 2010 12:55:03 +0200 Subject: [PATCH] nt/INSTALL: Add note about problematic characters passed to configure. --- nt/ChangeLog | 4 ++++ nt/INSTALL | 8 ++++++++ 2 files changed, 12 insertions(+) diff --git a/nt/ChangeLog b/nt/ChangeLog index 5dff8b27737..5f92bedd8c1 100644 --- a/nt/ChangeLog +++ b/nt/ChangeLog @@ -1,3 +1,7 @@ +2010-10-06 Juanma Barranquero + + * INSTALL: Add note about problematic characters passed to configure. + 2010-10-01 Eli Zaretskii * makefile.w32-in (frc, TAGS, TAGS-gmake, TAGS-nmake): New targets. diff --git a/nt/INSTALL b/nt/INSTALL index 8af8e3020de..c26ab196bd2 100644 --- 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. -- 2.11.4.GIT