[Please note this refers to a problem in the HTML online documentation of gmake 3.79 on www.gnu.org, not to gmake itself] Problem: Multiple occurrences of tokens which have '<' in them are not HTML encoded as they should be. This may be a bug in info2html or whatever tool was used to automatically generate these HTML pages. If so a different patch should be used and this one should be used only for detail-demonstration purposes. Patch: Here's a patch. It doesn't fix those instances where tokens like `$<' appear within <PRE> </PRE> tags. I believe these should be fixed as well even though they seem to be rendered correctly by Netscape and IE. --- make.html.orig Mon Nov 13 13:29:10 2000 +++ make.html Mon Nov 13 13:58:17 2000 @@ -2170,7 +2170,7 @@ </P> <P> Often the prerequisites include header files as well, which you do not -want to mention in the commands. The automatic variable <SAMP>`$<'</SAMP> is +want to mention in the commands. The automatic variable <SAMP>`$<'</SAMP> is just the first prerequisite: </P> @@ -2967,7 +2967,7 @@ </PRE> <P> -Here <SAMP>`$<'</SAMP> is the automatic variable that holds the name of the +Here <SAMP>`$<'</SAMP> is the automatic variable that holds the name of the prerequisite and <SAMP>`$@'</SAMP> is the automatic variable that holds the name of the target; see section <A HREF="make.html#SEC101">Automatic Variables</A>. @@ -9024,7 +9024,7 @@ <P> defines a rule that can make any file <TT>`<VAR>x</VAR>.o'</TT> from <TT>`<VAR>x</VAR>.c'</TT>. The command uses the automatic variables <SAMP>`$@'</SAMP> and -<SAMP>`$<'</SAMP> to substitute the names of the target file and the source file +<SAMP>`$<'</SAMP> to substitute the names of the target file and the source file in each case where the rule applies (see section <A HREF="make.html#SEC101">Automatic Variables</A>). </P> <P> @@ -9086,7 +9086,7 @@ What you do is use a special feature of <CODE>make</CODE>, the <STRONG>automatic variables</STRONG>. These variables have values computed afresh for each rule that is executed, based on the target and prerequisites of the rule. In this -example, you would use <SAMP>`$@'</SAMP> for the object file name and <SAMP>`$<'</SAMP> +example, you would use <SAMP>`$@'</SAMP> for the object file name and +<SAMP>`$<'</SAMP> for the source file name. </P> @@ -9117,7 +9117,7 @@ <A NAME="IDX844"></A> <A NAME="IDX845"></A> -<DT><CODE>$<</CODE> +<DT><CODE>$<</CODE> <DD> The name of the first prerequisite. If the target got its commands from an implicit rule, this will be the first prerequisite added by the @@ -9248,11 +9248,11 @@ <A NAME="IDX871"></A> <A NAME="IDX872"></A> -<DT><SAMP>`$(<D)'</SAMP> +<DT><SAMP>`$(<D)'</SAMP> <DD> <A NAME="IDX873"></A> <A NAME="IDX874"></A> -<DT><SAMP>`$(<F)'</SAMP> +<DT><SAMP>`$(<F)'</SAMP> <DD> The directory part and the file-within-directory part of the first prerequisite. @@ -9282,13 +9282,13 @@ <P> Note that we use a special stylistic convention when we talk about these -automatic variables; we write "the value of <SAMP>`$<'</SAMP>", rather than +automatic variables; we write "the value of <SAMP>`$<'</SAMP>", rather than "the variable <CODE><</CODE>" as we would write for ordinary variables such as <CODE>objects</CODE> and <CODE>CFLAGS</CODE>. We think this convention looks more natural in this special case. Please do not assume it has a -deep significance; <SAMP>`$<'</SAMP> refers to the variable named <CODE><</CODE> just +deep significance; <SAMP>`$<'</SAMP> refers to the variable named <CODE><</CODE> +just as <SAMP>`$(CFLAGS)'</SAMP> refers to the variable named <CODE>CFLAGS</CODE>. -You could just as well use <SAMP>`$(<)'</SAMP> in place of <SAMP>`$<'</SAMP>. +You could just as well use <SAMP>`$(<)'</SAMP> in place of <SAMP>`$<'</SAMP>. </P> @@ -10090,7 +10090,7 @@ <LI> -The automatic variables <CODE>$@</CODE>, <CODE>$*</CODE>, <CODE>$<</CODE>, <CODE>$%</CODE>, +The automatic variables <CODE>$@</CODE>, <CODE>$*</CODE>, <CODE>$<</CODE>, +<CODE>$%</CODE>, and <CODE>$?</CODE> have corresponding forms like <CODE>$(@F)</CODE> and <CODE>$(@D)</CODE>. We have generalized this to <CODE>$^</CODE> as an obvious extension. See section <A HREF="make.html#SEC101">Automatic Variables</A>. @@ -10550,7 +10550,7 @@ <P> When using GNU <CODE>make</CODE>, relying on <SAMP>`VPATH'</SAMP> to find the source file will work in the case where there is a single dependency file, -since the <CODE>make</CODE> automatic variable <SAMP>`$<'</SAMP> will represent the +since the <CODE>make</CODE> automatic variable <SAMP>`$<'</SAMP> will represent the source file wherever it is. (Many versions of <CODE>make</CODE> set <SAMP>`$<'</SAMP> only in implicit rules.) A Makefile target like @@ -11785,7 +11785,7 @@ <DD> The target member name, when the target is an archive member. -<DT><CODE>$<</CODE> +<DT><CODE>$<</CODE> <DD> The name of the first prerequisite. @@ -11828,11 +11828,11 @@ <DD> The directory part and the file-within-directory part of <CODE>$%</CODE>. -<DT><CODE>$(<D)</CODE> +<DT><CODE>$(<D)</CODE> <DD> -<DT><CODE>$(<F)</CODE> +<DT><CODE>$(<F)</CODE> <DD> -The directory part and the file-within-directory part of <CODE>$<</CODE>. +The directory part and the file-within-directory part of <CODE>$<</CODE>. <DT><CODE>$(^D)</CODE> <DD> @@ -13161,8 +13161,8 @@ <LI><A HREF="make.html#IDX869">$(%F)</A> <LI><A HREF="make.html#IDX863">$(*D)</A> <LI><A HREF="make.html#IDX865">$(*F)</A> -<LI><A HREF="make.html#IDX871">$(<D)</A> -<LI><A HREF="make.html#IDX873">$(<F)</A> +<LI><A HREF="make.html#IDX871">$(<D)</A> +<LI><A HREF="make.html#IDX873">$(<F)</A> <LI><A HREF="make.html#IDX879">$(?D)</A> <LI><A HREF="make.html#IDX881">$(?F)</A> <LI><A HREF="make.html#IDX859">$(@D)</A> @@ -13172,7 +13172,7 @@ <LI><A HREF="make.html#IDX856">$*</A> <LI><A HREF="make.html#IDX247">$*, and static pattern</A> <LI><A HREF="make.html#IDX854">$+</A> -<LI><A HREF="make.html#IDX844">$<</A> +<LI><A HREF="make.html#IDX844">$<</A> <LI><A HREF="make.html#IDX846">$?</A> <LI><A HREF="make.html#IDX840">$@</A> <LI><A HREF="make.html#IDX850">$^</A> _______________________________________________ Bug-make mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-make
