summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorPaul Smith <psmith@gnu.org>2022-09-13 18:22:29 -0400
committerPaul Smith <psmith@gnu.org>2022-09-13 18:22:29 -0400
commit88d126d6c4bcd2d97b6cedc729338a63990e8758 (patch)
treeb3023bce6d212cadb4b3aea8f7d9b6a904321102 /doc
parentf6ea899d83bf00fe9201fde0ca9cf7af8e443677 (diff)
downloadmake-git-88d126d6c4bcd2d97b6cedc729338a63990e8758.tar.gz
* doc/make.texi (Parallel Disable): Add clarifications.
* NEWS: Suggest how to change makefiles that use $(MAKEFLAGS).
Diffstat (limited to 'doc')
-rw-r--r--doc/make.texi9
1 files changed, 5 insertions, 4 deletions
diff --git a/doc/make.texi b/doc/make.texi
index 14ad2a37..dc9a5c95 100644
--- a/doc/make.texi
+++ b/doc/make.texi
@@ -4478,12 +4478,13 @@ If parallel execution is enabled, @code{make} will try to build @file{one} and
@file{two} in parallel but will not try to build @file{three} until both are
complete.
-As with targets provided to @code{.NOTPARALLEL}, @code{.WAIT} has an effect
+As with targets provided to @code{.NOTPARALLEL}, @code{.WAIT} takes effect
only when building the target in whose prerequisite list it appears. If the
same prerequisites are present in other targets, without @code{.WAIT}, then
-they may still be run in parallel. Because of this, @code{.WAIT} is an
-unreliable way to impose ordering than defining a prerequisite relationship.
-However it is easy to use and may suffice for simple needs.
+they may still be run in parallel. Because of this, neither
+@code{.NOTPARALLEL} with targets nor @code{.WAIT} are as reliable for
+controlling parallel execution as defining a prerequisite relationship.
+However they are easy to use and may be sufficient in less complex situations.
The @code{.WAIT} prerequisite will not be present in any of the automatic
variables for the rule.