Mercurial > emacs
changeset 110788:043e3c078a67
nt/INSTALL: Add note about problematic characters passed to configure.
| author | Juanma Barranquero <lekktu@gmail.com> |
|---|---|
| date | Wed, 06 Oct 2010 12:55:03 +0200 |
| parents | 1a4e0055489f |
| children | 12ce8eb76d37 |
| files | nt/ChangeLog nt/INSTALL |
| diffstat | 2 files changed, 12 insertions(+), 0 deletions(-) [+] |
line wrap: on
line diff
--- a/nt/ChangeLog Wed Oct 06 16:12:42 2010 +0900 +++ b/nt/ChangeLog Wed Oct 06 12:55:03 2010 +0200 @@ -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.
--- a/nt/INSTALL Wed Oct 06 16:12:42 2010 +0900 +++ b/nt/INSTALL Wed Oct 06 12:55:03 2010 +0200 @@ -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.