Fix `make setup dos', second try (#52622).

* builds/detect.mk (dos_setup): Don't use literal `>' character at
all.  Mixing the different escaping rules from make, dos, and
windows is too fragile.
This commit is contained in:
Werner Lemberg 2017-12-09 09:41:45 +01:00
parent 81dea49321
commit 286b0c9f33
2 changed files with 11 additions and 3 deletions

View File

@ -1,3 +1,11 @@
2017-12-08 Werner Lemberg <wl@gnu.org>
Fix `make setup dos', second try (#52622).
* builds/detect.mk (dos_setup): Don't use literal `>' character at
all. Mixing the different escaping rules from make, dos, and
windows is too fragile.
2017-12-08 Werner Lemberg <wl@gnu.org>
[docmaker] Fix code section parsing.

View File

@ -131,8 +131,8 @@ std_setup:
# Special case for Dos, Windows, OS/2, where echo "" doesn't work correctly!
#
# For `cmd.exe', we have to escape (unquoted) special characters like `>' as
# `^>', and we use 0xFF as a replacement character for a protected space.
# For `cmd.exe', we use 0xFF as a replacement character for a protected
# space.
#
dos_setup:
@type builds$(SEP)newline
@ -149,7 +149,7 @@ dos_setup:
@echo '$(CONFIG_MK)' from this directory then read the INSTALL file for help.
@type builds$(SEP)newline
@echo Otherwise, simply type 'make' again to build the library.
@echo or 'make refdoc' to build the API reference (this needs python ^>= 2.6).
@echo or 'make refdoc' to build the API reference (this needs at least python 2.6).
@type builds$(SEP)newline
@$(COPY) $(subst /,$(SEP),$(CONFIG_RULES) $(CONFIG_MK)) > nul