(Please Cc: me on any discussion, I'm not on bug-make.)
I've written some amendments to the "Rule Syntax" texinfo node file
to explain the problem with an `=' in a file name. And I put a
paragraph in the "Error Messages" node to help the user figure out
what happened.
Dale
diff -r make-3.79.1.orig/make.texinfo make-3.79.1.doc/make.texinfo
1536a1537,1542
> (Beware that if the first prerequisite contains an @samp{=}, the line
> will be interpreted as a target-specific variable assignment rather
> than as a rule. In the rare case
> that a file name contains @samp{=}, this can happen.
> @xref{Target-specific, ,Target-specific Variable Values}.)
>
9536,9538c9542,9551
< The second form is generated if the line has a semicolon as the first
< non-whitespace character; @code{make} interprets this to mean you left
< out the "target: prerequisite" section of a rule. @xref{Rule Syntax}.
- ---
> These messages can also happen if the preceding rule line was mistaken
> for a target-specific variable assignment because the first
> prerequisite of the rule contained a @samp{=}.
> @xref{Rule Syntax}.
> @xref{Target-specific, ,Target-specific Variable Values}.
>
> The second form is also generated if the line has a semicolon as the first
> non-whitespace character; @code{make} interprets this to mean that the
> line is a combined rule and command line, and that you left
> out the "target: prerequisite" section of the rule. @xref{Rule Syntax}.
_______________________________________________
Bug-make mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-make
