Commit 6072fed4 authored by Juanma Barranquero's avatar Juanma Barranquero
Browse files

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

parent 65f54520
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.
......
......@@ -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.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment