summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorPaul Smith <psmith@gnu.org>2020-12-07 01:03:11 -0500
committerPaul Smith <psmith@gnu.org>2020-12-07 01:03:11 -0500
commit9043b28250e0df7a6e5844b75f8ff2870337fc0a (patch)
treeb594d88a594c0d1bcae6b552583b26549c75e908 /doc
parentfcc11d05a60b061027a50b76d146c43306b20e32 (diff)
downloadmake-git-9043b28250e0df7a6e5844b75f8ff2870337fc0a.tar.gz
* doc/make.texi (How Patterns Match): [SV 58639] Fix chaining info.
Diffstat (limited to 'doc')
-rw-r--r--doc/make.texi8
1 files changed, 5 insertions, 3 deletions
diff --git a/doc/make.texi b/doc/make.texi
index b9588124..fe64ec26 100644
--- a/doc/make.texi
+++ b/doc/make.texi
@@ -10431,9 +10431,11 @@ A pattern rule can be used to build a given file only if there is a
target pattern that matches the file name, @emph{and} all
prerequisites in that rule either exist or can be built. The rules
you write take precedence over those that are built in. Note however,
-that a rule whose prerequisites actually exist or are mentioned always
-takes priority over a rule with prerequisites that must be made by
-chaining other implicit rules.
+that a rule which can be satisfied without chaining other implicit
+rules (for example, one which has no prerequisites or its
+prerequisites already exist or are mentioned) always takes priority
+over a rule with prerequisites that must be made by chaining other
+implicit rules.
@cindex stem, shortest
It is possible that more than one pattern rule will meet these