Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
6072fed4
Commit
6072fed4
authored
Oct 06, 2010
by
Juanma Barranquero
Browse files
nt/INSTALL: Add note about problematic characters passed to configure.
parent
65f54520
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
12 additions
and
0 deletions
+12
-0
nt/ChangeLog
nt/ChangeLog
+4
-0
nt/INSTALL
nt/INSTALL
+8
-0
No files found.
nt/ChangeLog
View file @
6072fed4
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.
...
...
nt/INSTALL
View file @
6072fed4
...
...
@@ -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.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment