aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoland McGrath <roland@redhat.com>1993-10-21 20:02:11 +0000
committerRoland McGrath <roland@redhat.com>1993-10-21 20:02:11 +0000
commit58d81fe699bcb465b36ff479cc5f74565da4811b (patch)
tree9a757202253f224857ab0aa78a44ec274f95dd25
parent4daf275eddefa17c0d703e3a613b77d3ba50d970 (diff)
downloadgunmake-58d81fe699bcb465b36ff479cc5f74565da4811b.tar.gz
Formerly make.texinfo.~121~
-rw-r--r--make.texinfo12
1 files changed, 10 insertions, 2 deletions
diff --git a/make.texinfo b/make.texinfo
index 9f32794..64dd5a6 100644
--- a/make.texinfo
+++ b/make.texinfo
@@ -9,8 +9,8 @@
@set EDITION 0.44
@set VERSION 3.69 Beta
-@set UPDATED 17 September 1993
-@set UPDATE-MONTH September 1993
+@set UPDATED 21 October 1993
+@set UPDATE-MONTH October 1993
@c finalout
@@ -8070,6 +8070,14 @@ strings. We feel it is much cleaner to always use automatic variables
and thus make this feature obsolete.@refill
@item
+In some Unix @code{make}s, the automatic variable @code{$*} appearing in
+the dependencies of a rule has the amazingly strange ``feature'' of
+expanding to the full name of the @emph{target of that rule}. We cannot
+imagine what went on in the minds of Unix @code{make} developers to do
+this; it is utterly inconsistent with the normal definition of @code{$*}.
+@vindex * @r{(automatic variable), unsupported bizarre usage}
+
+@item
In some Unix @code{make}s, implicit rule search
(@pxref{Implicit Rules, ,Using Implicit Rules}) is apparently done for
@emph{all} targets, not just those without commands. This means you can