Changeset 501 for vendor/gnumake/current/doc

Timestamp:

Sep 15, 2006, 4:30:32 AM (19 years ago)

Author:

bird

Message:

Load make-3.81/ into vendor/gnumake/current.

Location:

vendor/gnumake/current/doc

Files:

• .cvsignore (deleted)
• Makefile.am (modified) (1 diff)
• Makefile.in (modified) (18 diffs)
• fdl.texi (modified) (19 diffs)
• make-stds.texi (modified) (16 diffs)
• make.info (modified) (2 diffs)
• make.info-1 (modified) (202 diffs)
• make.info-2 (modified) (72 diffs)
• make.texi (modified) (72 diffs)
• stamp-vti (added)
• version.texi (added)

vendor/gnumake/current/doc/Makefile.am

@@ -1 +1 @@
 # -*-Makefile-*-, or close enough
+# Copyright (C) 2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software
+# Foundation, Inc.
+# This file is part of GNU Make.
+#
+# GNU Make is free software; you can redistribute it and/or modify it under the
+# terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2, or (at your option) any later version.
+#
+# GNU Make is distributed in the hope that it will be useful, but WITHOUT ANY
+# WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR
+# A PARTICULAR PURPOSE.  See the GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License along with
+# GNU Make; see the file COPYING.  If not, write to the Free Software
+# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
 
 TEXI2HTML = texi2html

vendor/gnumake/current/doc/Makefile.in

@@ -1 @@
-# Makefile.in generated by automake 1.8.2 from Makefile.am.
+# Makefile.in generated by automake 1.9.6 from Makefile.am.
 # @configure_input@
 
 # Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
-# 2003, 2004  Free Software Foundation, Inc.
+# 2003, 2004, 2005  Free Software Foundation, Inc.
 # This Makefile.in is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
@@ -16 +16 @@
 
 # -*-Makefile-*-, or close enough
+# Copyright (C) 2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software
+# Foundation, Inc.
+# This file is part of GNU Make.
+#
+# GNU Make is free software; you can redistribute it and/or modify it under the
+# terms of the GNU General Public License as published by the Free Software
+# Foundation; either version 2, or (at your option) any later version.
+#
+# GNU Make is distributed in the hope that it will be useful, but WITHOUT ANY
+# WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR
+# A PARTICULAR PURPOSE.  See the GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License along with
+# GNU Make; see the file COPYING.  If not, write to the Free Software
+# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
 srcdir = @srcdir@
 top_srcdir = @top_srcdir@
@@ -36 +51 @@
 PRE_UNINSTALL = :
 POST_UNINSTALL = :
+build_triplet = @build@
 host_triplet = @host@
 subdir = doc
 DIST_COMMON = $(make_TEXINFOS) $(srcdir)/Makefile.am \
-        $(srcdir)/Makefile.in
+        $(srcdir)/Makefile.in $(srcdir)/stamp-vti \
+        $(srcdir)/version.texi
 ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
 am__aclocal_m4_deps = $(top_srcdir)/config/dospaths.m4 \
@@ -68 +85 @@
 AM_MAKEINFOHTMLFLAGS = $(AM_MAKEINFOFLAGS)
 DVIPS = dvips
-am__installdirs = $(DESTDIR)$(infodir)
+am__installdirs = "$(DESTDIR)$(infodir)"
 DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
 ACLOCAL = @ACLOCAL@
@@ -139 +156 @@
 USE_NLS = @USE_NLS@
 VERSION = @VERSION@
+WINDOWSENV_FALSE = @WINDOWSENV_FALSE@
+WINDOWSENV_TRUE = @WINDOWSENV_TRUE@
 XGETTEXT = @XGETTEXT@
 ac_ct_CC = @ac_ct_CC@
@@ -148 +167 @@
 am__leading_dot = @am__leading_dot@
 am__quote = @am__quote@
+am__tar = @am__tar@
+am__untar = @am__untar@
 bindir = @bindir@
 build = @build@
@@ -216 +237 @@
 
 .texi.info:
-        restore=: && \
-        backupdir="$(am__leading_dot)am$$$$" && \
+        restore=: && backupdir="$(am__leading_dot)am$$$$" && \
         am__cwd=`pwd` && cd $(srcdir) && \
         rm -rf $$backupdir && mkdir $$backupdir && \
-        for f in $@ $@-[0-9] $@-[0-9][0-9] $(@:.info=).i[0-9] $(@:.info=).i[0-9][0-9]; do \
-          if test -f $$f; then \
-            mv $$f $$backupdir; \
-            restore=mv; \
-          fi; \
-        done; \
+        if ($(MAKEINFO) --version) >/dev/null 2>&1; then \
+          for f in $@ $@-[0-9] $@-[0-9][0-9] $(@:.info=).i[0-9] $(@:.info=).i[0-9][0-9]; do \
+            if test -f $$f; then mv $$f $$backupdir; restore=mv; else :; fi; \
+          done; \
+        else :; fi && \
         cd "$$am__cwd"; \
         if $(MAKEINFO) $(AM_MAKEINFOFLAGS) $(MAKEINFOFLAGS) -I $(srcdir) \
@@ -237 +256 @@
           $$restore $$backupdir/* `echo "./$@" | sed 's|[^/]*$$||'`; \
         fi; \
-        rm -rf $$backupdir; \
-        exit $$rc
+        rm -rf $$backupdir; exit $$rc
 
 .texi.dvi:
@@ -251 +269 @@
 
 .texi.html:
-        $(MAKEINFOHTML) $(AM_MAKEINFOHTMLFLAGS) $(MAKEINFOFLAGS) -I $(srcdir) \
-         -o $@ $<
-        if test ! -d $@ && test -d $(@:.html=); then \
-          mv $(@:.html=) $@; else :; fi
-$(srcdir)/make.info: make.texi $(make_TEXINFOS)
-make.dvi: make.texi $(make_TEXINFOS)
-make.pdf: make.texi $(make_TEXINFOS)
-make.html: make.texi $(make_TEXINFOS)
+        rm -rf $(@:.html=.htp)
+        if $(MAKEINFOHTML) $(AM_MAKEINFOHTMLFLAGS) $(MAKEINFOFLAGS) -I $(srcdir) \
+         -o $(@:.html=.htp) $<; \
+        then \
+          rm -rf $@; \
+          if test ! -d $(@:.html=.htp) && test -d $(@:.html=); then \
+            mv $(@:.html=) $@; else mv $(@:.html=.htp) $@; fi; \
+        else \
+          if test ! -d $(@:.html=.htp) && test -d $(@:.html=); then \
+            rm -rf $(@:.html=); else rm -Rf $(@:.html=.htp) $@; fi; \
+          exit 1; \
+        fi
+$(srcdir)/make.info: make.texi $(srcdir)/version.texi $(make_TEXINFOS)
+make.dvi: make.texi $(srcdir)/version.texi $(make_TEXINFOS)
+make.pdf: make.texi $(srcdir)/version.texi $(make_TEXINFOS)
+make.html: make.texi $(srcdir)/version.texi $(make_TEXINFOS)
+$(srcdir)/version.texi:  $(srcdir)/stamp-vti
+$(srcdir)/stamp-vti: make.texi $(top_srcdir)/configure
+        @(dir=.; test -f ./make.texi || dir=$(srcdir); \
+        set `$(SHELL) $(top_srcdir)/config/mdate-sh $$dir/make.texi`; \
+        echo "@set UPDATED $$1 $$2 $$3"; \
+        echo "@set UPDATED-MONTH $$2 $$3"; \
+        echo "@set EDITION $(VERSION)"; \
+        echo "@set VERSION $(VERSION)") > vti.tmp
+        @cmp -s vti.tmp $(srcdir)/version.texi \
+          || (echo "Updating $(srcdir)/version.texi"; \
+              cp vti.tmp $(srcdir)/version.texi)
+        -@rm -f vti.tmp
+        @cp $(srcdir)/version.texi $@
+
+mostlyclean-vti:
+        -rm -f vti.tmp
+
+maintainer-clean-vti:
+        -rm -f $(srcdir)/stamp-vti $(srcdir)/version.texi
 .dvi.ps:
+        TEXINPUTS="$(am__TEXINFO_TEX_DIR)$(PATH_SEPARATOR)$$TEXINPUTS" \
         $(DVIPS) -o $@ $<
 
 uninstall-info-am:
-        $(PRE_UNINSTALL)
+        @$(PRE_UNINSTALL)
         @if (install-info --version && \
              install-info --version 2>&1 | sed 1q | grep -i -v debian) >/dev/null 2>&1; then \
@@ -269 +315 @@
           for file in $$list; do \
             relfile=`echo "$$file" | sed 's|^.*/||'`; \
-            echo " install-info --info-dir=$(DESTDIR)$(infodir) --remove $(DESTDIR)$(infodir)/$$relfile"; \
-            install-info --info-dir=$(DESTDIR)$(infodir) --remove $(DESTDIR)$(infodir)/$$relfile; \
+            echo " install-info --info-dir='$(DESTDIR)$(infodir)' --remove '$(DESTDIR)$(infodir)/$$relfile'"; \
+            install-info --info-dir="$(DESTDIR)$(infodir)" --remove "$(DESTDIR)$(infodir)/$$relfile"; \
           done; \
         else :; fi
@@ -278 +324 @@
           relfile=`echo "$$file" | sed 's|^.*/||'`; \
           relfile_i=`echo "$$relfile" | sed 's|\.info$$||;s|$$|.i|'`; \
-          (if cd $(DESTDIR)$(infodir); then \
-             echo " rm -f $$relfile $$relfile-[0-9] $$relfile-[0-9][0-9] $$relfile_i[0-9] $$relfile_i[0-9][0-9])"; \
+          (if cd "$(DESTDIR)$(infodir)"; then \
+             echo " cd '$(DESTDIR)$(infodir)' && rm -f $$relfile $$relfile-[0-9] $$relfile-[0-9][0-9] $$relfile_i[0-9] $$relfile_i[0-9][0-9]"; \
              rm -f $$relfile $$relfile-[0-9] $$relfile-[0-9][0-9] $$relfile_i[0-9] $$relfile_i[0-9][0-9]; \
            else :; fi); \
@@ -351 +397 @@
 all-am: Makefile $(INFO_DEPS)
 installdirs:
-        $(mkdir_p) $(DESTDIR)$(infodir)
+        for dir in "$(DESTDIR)$(infodir)"; do \
+          test -z "$$dir" || $(mkdir_p) "$$dir"; \
+        done
 install: install-am
 install-exec: install-exec-am
@@ -372 +420 @@
 
 distclean-generic:
-        -rm -f $(CONFIG_CLEAN_FILES)
+        -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
 
 maintainer-clean-generic:
@@ -403 +451 @@
 install-info-am: $(INFO_DEPS)
         @$(NORMAL_INSTALL)
-        $(mkdir_p) $(DESTDIR)$(infodir)
+        test -z "$(infodir)" || $(mkdir_p) "$(DESTDIR)$(infodir)"
         @srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`; \
         list='$(INFO_DEPS)'; \
@@ -416 +464 @@
             if test -f $$ifile; then \
               relfile=`echo "$$ifile" | sed 's|^.*/||'`; \
-              echo " $(INSTALL_DATA) $$ifile $(DESTDIR)$(infodir)/$$relfile"; \
-              $(INSTALL_DATA) $$ifile $(DESTDIR)$(infodir)/$$relfile; \
+              echo " $(INSTALL_DATA) '$$ifile' '$(DESTDIR)$(infodir)/$$relfile'"; \
+              $(INSTALL_DATA) "$$ifile" "$(DESTDIR)$(infodir)/$$relfile"; \
             else : ; fi; \
           done; \
@@ -427 +475 @@
           for file in $$list; do \
             relfile=`echo "$$file" | sed 's|^.*/||'`; \
-            echo " install-info --info-dir=$(DESTDIR)$(infodir) $(DESTDIR)$(infodir)/$$relfile";\
-            install-info --info-dir=$(DESTDIR)$(infodir) $(DESTDIR)$(infodir)/$$relfile || :;\
+            echo " install-info --info-dir='$(DESTDIR)$(infodir)' '$(DESTDIR)$(infodir)/$$relfile'";\
+            install-info --info-dir="$(DESTDIR)$(infodir)" "$(DESTDIR)$(infodir)/$$relfile" || :;\
           done; \
         else : ; fi
@@ -438 +486 @@
         -rm -f Makefile
 maintainer-clean-am: distclean-am maintainer-clean-aminfo \
-        maintainer-clean-generic
+        maintainer-clean-generic maintainer-clean-vti
 
 mostlyclean: mostlyclean-am
 
-mostlyclean-am: mostlyclean-aminfo mostlyclean-generic
+mostlyclean-am: mostlyclean-aminfo mostlyclean-generic mostlyclean-vti
 
 pdf: pdf-am
@@ -460 +508 @@
         install-man install-strip installcheck installcheck-am \
         installdirs maintainer-clean maintainer-clean-aminfo \
-        maintainer-clean-generic mostlyclean mostlyclean-aminfo \
-        mostlyclean-generic pdf pdf-am ps ps-am uninstall uninstall-am \
-        uninstall-info-am
+        maintainer-clean-generic maintainer-clean-vti mostlyclean \
+        mostlyclean-aminfo mostlyclean-generic mostlyclean-vti pdf \
+        pdf-am ps ps-am uninstall uninstall-am uninstall-info-am
 
 

vendor/gnumake/current/doc/fdl.texi

@@ -4 +4 @@
 
 @cindex FDL, GNU Free Documentation License
-@center Version 1.1, March 2000
+@center Version 1.2, November 2002
 
 @display
-Copyright @copyright{} 2000 Free Software Foundation, Inc.
-59 Temple Place, Suite 330, Boston, MA  02111-1307, USA
+Copyright @copyright{} 2000,2001,2002 Free Software Foundation, Inc.
+51 Franklin St, Fifth Floor, Boston, MA  02110-1301, USA
 
 Everyone is permitted to copy and distribute verbatim copies
@@ -19 +19 @@
 
 The purpose of this License is to make a manual, textbook, or other
-written document @dfn{free} in the sense of freedom: to assure everyone
-the effective freedom to copy and redistribute it, with or without
-modifying it, either commercially or noncommercially.  Secondarily,
-this License preserves for the author and publisher a way to get
-credit for their work, while not being considered responsible for
-modifications made by others.
+functional and useful document @dfn{free} in the sense of freedom: to
+assure everyone the effective freedom to copy and redistribute it,
+with or without modifying it, either commercially or noncommercially.
+Secondarily, this License preserves for the author and publisher a way
+to get credit for their work, while not being considered responsible
+for modifications made by others.
 
 This License is a kind of ``copyleft'', which means that derivative
@@ -42 +42 @@
 APPLICABILITY AND DEFINITIONS
 
-This License applies to any manual or other work that contains a
-notice placed by the copyright holder saying it can be distributed
-under the terms of this License.  The ``Document'', below, refers to any
-such manual or work.  Any member of the public is a licensee, and is
-addressed as ``you''.
+This License applies to any manual or other work, in any medium, that
+contains a notice placed by the copyright holder saying it can be
+distributed under the terms of this License.  Such a notice grants a
+world-wide, royalty-free license, unlimited in duration, to use that
+work under the conditions stated herein.  The ``Document'', below,
+refers to any such manual or work.  Any member of the public is a
+licensee, and is addressed as ``you''.  You accept the license if you
+copy, modify or distribute the work in a way requiring permission
+under copyright law.
 
 A ``Modified Version'' of the Document means any work containing the
@@ -52 +56 @@
 modifications and/or translated into another language.
 
-A ``Secondary Section'' is a named appendix or a front-matter section of
-the Document that deals exclusively with the relationship of the
-publishers or authors of the Document to the Document's overall subject
-(or to related matters) and contains nothing that could fall directly
-within that overall subject.  (For example, if the Document is in part a
-textbook of mathematics, a Secondary Section may not explain any
-mathematics.)  The relationship could be a matter of historical
+A ``Secondary Section'' is a named appendix or a front-matter section
+of the Document that deals exclusively with the relationship of the
+publishers or authors of the Document to the Document's overall
+subject (or to related matters) and contains nothing that could fall
+directly within that overall subject.  (Thus, if the Document is in
+part a textbook of mathematics, a Secondary Section may not explain
+any mathematics.)  The relationship could be a matter of historical
 connection with the subject or with related matters, or of legal,
 commercial, philosophical, ethical or political position regarding
@@ -65 +69 @@
 The ``Invariant Sections'' are certain Secondary Sections whose titles
 are designated, as being those of Invariant Sections, in the notice
-that says that the Document is released under this License.
+that says that the Document is released under this License.  If a
+section does not fit the above definition of Secondary then it is not
+allowed to be designated as Invariant.  The Document may contain zero
+Invariant Sections.  If the Document does not identify any Invariant
+Sections then there are none.
 
 The ``Cover Texts'' are certain short passages of text that are listed,
 as Front-Cover Texts or Back-Cover Texts, in the notice that says that
-the Document is released under this License.
+the Document is released under this License.  A Front-Cover Text may
+be at most 5 words, and a Back-Cover Text may be at most 25 words.
 
 A ``Transparent'' copy of the Document means a machine-readable copy,
 represented in a format whose specification is available to the
-general public, whose contents can be viewed and edited directly and
+general public, that is suitable for revising the document
 straightforwardly with generic text editors or (for images composed of
 pixels) generic paint programs or (for drawings) some widely available
@@ -79 +88 @@
 for automatic translation to a variety of formats suitable for input
 to text formatters.  A copy made in an otherwise Transparent file
-format whose markup has been designed to thwart or discourage
-subsequent modification by readers is not Transparent.  A copy that is
-not ``Transparent'' is called ``Opaque''.
+format whose markup, or absence of markup, has been arranged to thwart
+or discourage subsequent modification by readers is not Transparent.
+An image format is not Transparent if used for any substantial amount
+of text.  A copy that is not ``Transparent'' is called ``Opaque''.
 
 Examples of suitable formats for Transparent copies include plain
-@sc{ascii} without markup, Texinfo input format, La@TeX{} input format,
-@acronym{SGML} or @acronym{XML} using a publicly available
-@acronym{DTD}, and standard-conforming simple @acronym{HTML} designed
-for human modification.  Opaque formats include PostScript,
-@acronym{PDF}, proprietary formats that can be read and edited only by
-proprietary word processors, @acronym{SGML} or @acronym{XML} for which
-the @acronym{DTD} and/or processing tools are not generally available,
-and the machine-generated @acronym{HTML} produced by some word
-processors for output purposes only.
+@sc{ascii} without markup, Texinfo input format, La@TeX{} input
+format, @acronym{SGML} or @acronym{XML} using a publicly available
+@acronym{DTD}, and standard-conforming simple @acronym{HTML},
+PostScript or @acronym{PDF} designed for human modification.  Examples
+of transparent image formats include @acronym{PNG}, @acronym{XCF} and
+@acronym{JPG}.  Opaque formats include proprietary formats that can be
+read and edited only by proprietary word processors, @acronym{SGML} or
+@acronym{XML} for which the @acronym{DTD} and/or processing tools are
+not generally available, and the machine-generated @acronym{HTML},
+PostScript or @acronym{PDF} produced by some word processors for
+output purposes only.
 
 The ``Title Page'' means, for a printed book, the title page itself,
@@ -100 +112 @@
 the text near the most prominent appearance of the work's title,
 preceding the beginning of the body of the text.
+
+A section ``Entitled XYZ'' means a named subunit of the Document whose
+title either is precisely XYZ or contains XYZ in parentheses following
+text that translates XYZ in another language.  (Here XYZ stands for a
+specific section name mentioned below, such as ``Acknowledgements'',
+``Dedications'', ``Endorsements'', or ``History''.)  To ``Preserve the Title''
+of such a section when you modify the Document means that it remains a
+section ``Entitled XYZ'' according to this definition.
+
+The Document may include Warranty Disclaimers next to the notice which
+states that this License applies to the Document.  These Warranty
+Disclaimers are considered to be included by reference in this
+License, but only as regards disclaiming warranties: any other
+implication that these Warranty Disclaimers may have is void and has
+no effect on the meaning of this License.
 
 @item
@@ -120 +147 @@
 COPYING IN QUANTITY
 
-If you publish printed copies of the Document numbering more than 100,
-and the Document's license notice requires Cover Texts, you must enclose
-the copies in covers that carry, clearly and legibly, all these Cover
+If you publish printed copies (or copies in media that commonly have
+printed covers) of the Document, numbering more than 100, and the
+Document's license notice requires Cover Texts, you must enclose the
+copies in covers that carry, clearly and legibly, all these Cover
 Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on
 the back cover.  Both covers must also clearly and legibly identify
@@ -140 +168 @@
 more than 100, you must either include a machine-readable Transparent
 copy along with each Opaque copy, or state in or with each Opaque copy
-a publicly-accessible computer-network location containing a complete
-Transparent copy of the Document, free of added material, which the
-general network-using public has access to download anonymously at no
-charge using public-standard network protocols.  If you use the latter
-option, you must take reasonably prudent steps, when you begin
-distribution of Opaque copies in quantity, to ensure that this
-Transparent copy will remain thus accessible at the stated location
-until at least one year after the last time you distribute an Opaque
-copy (directly or through your agents or retailers) of that edition to
-the public.
+a computer-network location from which the general network-using
+public has access to download using public-standard network protocols
+a complete Transparent copy of the Document, free of added material.
+If you use the latter option, you must take reasonably prudent steps,
+when you begin distribution of Opaque copies in quantity, to ensure
+that this Transparent copy will remain thus accessible at the stated
+location until at least one year after the last time you distribute an
+Opaque copy (directly or through your agents or retailers) of that
+edition to the public.
 
 It is requested, but not required, that you contact the authors of the
@@ -177 +204 @@
 responsible for authorship of the modifications in the Modified
 Version, together with at least five of the principal authors of the
-Document (all of its principal authors, if it has less than five).
+Document (all of its principal authors, if it has fewer than five),
+unless they release you from this requirement.
 
 @item
@@ -203 +231 @@
 
 @item
-Preserve the section entitled ``History'', and its title, and add to
-it an item stating at least the title, year, new authors, and
+Preserve the section Entitled ``History'', Preserve its Title, and add
+to it an item stating at least the title, year, new authors, and
 publisher of the Modified Version as given on the Title Page.  If
-there is no section entitled ``History'' in the Document, create one
+there is no section Entitled ``History'' in the Document, create one
 stating the title, year, authors, and publisher of the Document as
 given on its Title Page, then add an item describing the Modified
@@ -221 +249 @@
 
 @item
-In any section entitled ``Acknowledgments'' or ``Dedications'',
-preserve the section's title, and preserve in the section all the
-substance and tone of each of the contributor acknowledgments
-and/or dedications given therein.
+For any section Entitled ``Acknowledgements'' or ``Dedications'', Preserve
+the Title of the section, and preserve in the section all the
+substance and tone of each of the contributor acknowledgements and/or
+dedications given therein.
 
 @item
@@ -232 +260 @@
 
 @item
-Delete any section entitled ``Endorsements''.  Such a section
+Delete any section Entitled ``Endorsements''.  Such a section
 may not be included in the Modified Version.
 
 @item
-Do not retitle any existing section as ``Endorsements''
-or to conflict in title with any Invariant Section.
+Do not retitle any existing section to be Entitled ``Endorsements'' or
+to conflict in title with any Invariant Section.
+
+@item
+Preserve any Warranty Disclaimers.
 @end enumerate
 
@@ -247 +278 @@
 These titles must be distinct from any other section titles.
 
-You may add a section entitled ``Endorsements'', provided it contains
+You may add a section Entitled ``Endorsements'', provided it contains
 nothing but endorsements of your Modified Version by various
 parties---for example, statements of peer review or that the text has
@@ -275 +306 @@
 Invariant Sections of all of the original documents, unmodified, and
 list them all as Invariant Sections of your combined work in its
-license notice.
+license notice, and that you preserve all their Warranty Disclaimers.
 
 The combined work need only contain one copy of this License, and
@@ -286 +317 @@
 Invariant Sections in the license notice of the combined work.
 
-In the combination, you must combine any sections entitled ``History''
-in the various original documents, forming one section entitled
-``History''; likewise combine any sections entitled ``Acknowledgments'',
-and any sections entitled ``Dedications''.  You must delete all sections
-entitled ``Endorsements.''
+In the combination, you must combine any sections Entitled ``History''
+in the various original documents, forming one section Entitled
+``History''; likewise combine any sections Entitled ``Acknowledgements'',
+and any sections Entitled ``Dedications''.  You must delete all
+sections Entitled ``Endorsements.''
 
 @item
@@ -311 +342 @@
 A compilation of the Document or its derivatives with other separate
 and independent documents or works, in or on a volume of a storage or
-distribution medium, does not as a whole count as a Modified Version
-of the Document, provided no compilation copyright is claimed for the
-compilation.  Such a compilation is called an ``aggregate'', and this
-License does not apply to the other self-contained works thus compiled
-with the Document, on account of their being thus compiled, if they
-are not themselves derivative works of the Document.
+distribution medium, is called an ``aggregate'' if the copyright
+resulting from the compilation is not used to limit the legal rights
+of the compilation's users beyond what the individual works permit.
+When the Document is included in an aggregate, this License does not
+apply to the other works in the aggregate which are not themselves
+derivative works of the Document.
 
 If the Cover Text requirement of section 3 is applicable to these
-copies of the Document, then if the Document is less than one quarter
-of the entire aggregate, the Document's Cover Texts may be placed on
-covers that surround only the Document within the aggregate.
-Otherwise they must appear on covers around the whole aggregate.
+copies of the Document, then if the Document is less than one half of
+the entire aggregate, the Document's Cover Texts may be placed on
+covers that bracket the Document within the aggregate, or the
+electronic equivalent of covers if the Document is in electronic form.
+Otherwise they must appear on printed covers that bracket the whole
+aggregate.
 
 @item
@@ -333 +366 @@
 translations of some or all Invariant Sections in addition to the
 original versions of these Invariant Sections.  You may include a
-translation of this License provided that you also include the
-original English version of this License.  In case of a disagreement
-between the translation and the original English version of this
-License, the original English version will prevail.
+translation of this License, and all the license notices in the
+Document, and any Warranty Disclaimers, provided that you also include
+the original English version of this License and the original versions
+of those notices and disclaimers.  In case of a disagreement between
+the translation and the original version of this License or a notice
+or disclaimer, the original version will prevail.
+
+If a section in the Document is Entitled ``Acknowledgements'',
+``Dedications'', or ``History'', the requirement (section 4) to Preserve
+its Title (section 1) will typically require changing the actual
+title.
 
 @item
@@ -379 +419 @@
   Copyright (C)  @var{year}  @var{your name}.
   Permission is granted to copy, distribute and/or modify this document
-  under the terms of the GNU Free Documentation License, Version 1.1
+  under the terms of the GNU Free Documentation License, Version 1.2
   or any later version published by the Free Software Foundation;
-  with the Invariant Sections being @var{list their titles}, with the
-  Front-Cover Texts being @var{list}, and with the Back-Cover Texts being @var{list}.
-  A copy of the license is included in the section entitled ``GNU
+  with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
+  Texts.  A copy of the license is included in the section entitled ``GNU
   Free Documentation License''.
 @end group
 @end smallexample
 
-If you have no Invariant Sections, write ``with no Invariant Sections''
-instead of saying which ones are invariant.  If you have no
-Front-Cover Texts, write ``no Front-Cover Texts'' instead of
-``Front-Cover Texts being @var{list}''; likewise for Back-Cover Texts.
+If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts,
+replace the ``with...Texts.'' line with this:
+
+@smallexample
+@group
+    with the Invariant Sections being @var{list their titles}, with
+    the Front-Cover Texts being @var{list}, and with the Back-Cover Texts
+    being @var{list}.
+@end group
+@end smallexample
+
+If you have Invariant Sections without Cover Texts, or some other
+combination of the three, merge those two alternatives to suit the
+situation.
 
 If your document contains nontrivial examples of program code, we

vendor/gnumake/current/doc/make-stds.texi

@@ -9 +9 @@
 @cindex standards for makefiles
 
-@c Copyright 1992, 1993, 1994, 1995, 1996, 1997, 1998, 2000, 2001 Free
-@c Software Foundation, Inc.
+@c Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 2000, 2001,
+@c 2004, 2005 Free Software Foundation, Inc.
 
 @c Permission is granted to copy, distribute and/or modify this document
@@ -294 +294 @@
 Installation directories should always be named by variables, so it is
 easy to install in a nonstandard place.  The standard names for these
-variables are described below.  They are based on a standard filesystem
-layout; variants of it are used in SVR4, 4.4BSD, GNU/Linux, Ultrix v4,
-and other modern operating systems.
+variables and the values they should have in GNU packages are
+described below.  They are based on a standard filesystem layout;
+variants of it are used in GNU/Linux and other modern operating
+systems.
+
+Installers are expected to override these values when calling
+@command{make} (e.g., @kbd{make prefix=/usr install} or
+@command{configure} (e.g., @kbd{configure --prefix=/usr}).  GNU
+packages should not try to guess which value should be appropriate for
+these variables on the system they are being installed onto: use the
+default settings specified here so that all GNU packages behave
+identically, allowing the installer to achieve any desired layout.
 
 These two variables set the root for the installation.  All the other
@@ -356 +365 @@
 @file{/usr/local/libexec}, but write it as @file{$(exec_prefix)/libexec}.
 (If you are using Autoconf, write it as @samp{@@libexecdir@@}.)
+
+The definition of @samp{libexecdir} is the same for all packages, so
+you should install your data in a subdirectory thereof.  Most packages
+install their data under @file{$(libexecdir)/@var{package-name}/},
+possibly within additional subdirectories thereof, such as
+@file{$(libexecdir)/@var{package-name}/@var{machine}/@var{version}}.
 @end table
 
@@ -378 +393 @@
 architecture-independent, and it is generally not hard.
 
-Therefore, here are the variables Makefiles should use to specify
-directories:
+Here are the variables Makefiles should use to specify directories
+to put these various kinds of files in:
 
 @table @samp
+@item datarootdir
+The root of the directory tree for read-only architecture-independent
+data files.  This should normally be @file{/usr/local/share}, but
+write it as @file{$(prefix)/share}.  (If you are using Autoconf, write
+it as @samp{@@datarootdir@@}.)  @samp{datadir}'s default value is
+based on this variable; so are @samp{infodir}, @samp{mandir}, and
+others.
+
 @item datadir
-The directory for installing read-only architecture independent data
-files.  This should normally be @file{/usr/local/share}, but write it as
-@file{$(prefix)/share}.
-(If you are using Autoconf, write it as @samp{@@datadir@@}.)
-As a special exception, see @file{$(infodir)}
-and @file{$(includedir)} below.
+The directory for installing idiosyncratic read-only
+architecture-independent data files for this program.  This is usually
+the same place as @samp{datarootdir}, but we use the two separate
+variables so that you can move these program-specific files without
+altering the location for Info files, man pages, etc.
+
+This should normally be @file{/usr/local/share}, but write it as
+@file{$(datarootdir)}.  (If you are using Autoconf, write it as
+@samp{@@datadir@@}.)
+
+The definition of @samp{datadir} is the same for all packages, so you
+should install your data in a subdirectory thereof.  Most packages
+install their data under @file{$(datadir)/@var{package-name}/}.
 
 @item sysconfdir
@@ -420 +450 @@
 @file{$(prefix)/var}.
 (If you are using Autoconf, write it as @samp{@@localstatedir@@}.)
-
-@item libdir
-The directory for object files and libraries of object code.  Do not
-install executables here, they probably ought to go in @file{$(libexecdir)}
-instead.  The value of @code{libdir} should normally be
-@file{/usr/local/lib}, but write it as @file{$(exec_prefix)/lib}.
-(If you are using Autoconf, write it as @samp{@@libdir@@}.)
-
-@item infodir
-The directory for installing the Info files for this package.  By
-default, it should be @file{/usr/local/info}, but it should be written
-as @file{$(prefix)/info}.
-(If you are using Autoconf, write it as @samp{@@infodir@@}.)
-
-@item lispdir
-The directory for installing any Emacs Lisp files in this package.  By
-default, it should be @file{/usr/local/share/emacs/site-lisp}, but it
-should be written as @file{$(prefix)/share/emacs/site-lisp}.
-
-If you are using Autoconf, write the default as @samp{@@lispdir@@}.
-In order to make @samp{@@lispdir@@} work, you need the following lines
-in your @file{configure.in} file:
-
-@example
-lispdir='$@{datadir@}/emacs/site-lisp'
-AC_SUBST(lispdir)
-@end example
-
+@end table
+
+These variables specify the directory for installing certain specific
+types of files, if your program has them.  Every GNU package should
+have Info files, so every program needs @samp{infodir}, but not all
+need @samp{libdir} or @samp{lispdir}.
+
+@table @samp
 @item includedir
 @c rewritten to avoid overfull hbox --roland
@@ -482 +492 @@
 To tell whether @file{foo.h} came from the Foo package, put a magic
 string in the file---part of a comment---and @code{grep} for that string.
+
+@item docdir
+The directory for installing documentation files (other than Info) for
+this package.  By default, it should be
+@file{/usr/local/share/doc/@var{yourpkg}}, but it should be written as
+@file{$(datarootdir)/doc/@var{yourpkg}}.  (If you are using Autoconf,
+write it as @samp{@@docdir@@}.)  The @var{yourpkg} subdirectory, which
+may include a version number, prevents collisions among files with
+common names, such as @file{README}.
+
+@item infodir
+The directory for installing the Info files for this package.  By
+default, it should be @file{/usr/local/share/info}, but it should be
+written as @file{$(datarootdir)/info}.  (If you are using Autoconf,
+write it as @samp{@@infodir@@}.)  @code{infodir} is separate from
+@code{docdir} for compatibility with existing practice.
+
+@item htmldir
+@itemx dvidir
+@itemx pdfdir
+@itemx psdir
+Directories for installing documentation files in the particular
+format.  (It is not required to support documentation in all these
+formats.)  They should all be set to @code{$(docdir)} by default.  (If
+you are using Autoconf, write them as @samp{@@htmldir@@},
+@samp{@@dvidir@@}, etc.)  Packages which supply several translations
+of their documentation should install them in
+@samp{$(htmldir)/}@var{ll}, @samp{$(pdfdir)/}@var{ll}, etc. where
+@var{ll} is a locale abbreviation such as @samp{en} or @samp{pt_BR}.
+
+@item libdir
+The directory for object files and libraries of object code.  Do not
+install executables here, they probably ought to go in @file{$(libexecdir)}
+instead.  The value of @code{libdir} should normally be
+@file{/usr/local/lib}, but write it as @file{$(exec_prefix)/lib}.
+(If you are using Autoconf, write it as @samp{@@libdir@@}.)
+
+@item lispdir
+The directory for installing any Emacs Lisp files in this package.  By
+default, it should be @file{/usr/local/share/emacs/site-lisp}, but it
+should be written as @file{$(datarootdir)/emacs/site-lisp}.
+
+If you are using Autoconf, write the default as @samp{@@lispdir@@}.
+In order to make @samp{@@lispdir@@} work, you need the following lines
+in your @file{configure.in} file:
+
+@example
+lispdir='$@{datarootdir@}/emacs/site-lisp'
+AC_SUBST(lispdir)
+@end example
+
+@item localedir
+The directory for installing locale-specific message catalogs for this
+package.  By default, it should be @file{/usr/local/share/locale}, but
+it should be written as @file{$(datarootdir)/locale}.  (If you are
+using Autoconf, write it as @samp{@@localedir@@}.)  This directory
+usually has a subdirectory per locale.
 @end table
 
@@ -489 +556 @@
 @item mandir
 The top-level directory for installing the man pages (if any) for this
-package.  It will normally be @file{/usr/local/man}, but you should
-write it as @file{$(prefix)/man}.
-(If you are using Autoconf, write it as @samp{@@mandir@@}.)
+package.  It will normally be @file{/usr/local/share/man}, but you
+should write it as @file{$(datarootdir)/man}.  (If you are using
+Autoconf, write it as @samp{@@mandir@@}.)
 
 @item man1dir
@@ -536 +603 @@
 # NOTE: This directory must exist when you start the install.
 prefix = /usr/local
+datarootdir = $(prefix)/share
+datadir = $(datarootdir)
 exec_prefix = $(prefix)
 # Where to put the executable for the command `gcc'.
@@ -542 +611 @@
 libexecdir = $(exec_prefix)/libexec
 # Where to put the Info files.
-infodir = $(prefix)/info
+infodir = $(datarootdir)/info
 @end smallexample
 
@@ -631 +700 @@
 Categories}.
 
+@item install-html
+@itemx install-dvi
+@itemx install-pdf
+@itemx install-ps
+These targets install documentation in formats other than Info;
+they're intended to be called explicitly by the person installing the
+package, if that format is desired.  GNU prefers Info files, so these
+must be installed by the @code{install} target.
+
+When you have many documentation files to install, we recommend that
+you avoid collisions and clutter by arranging for these targets to
+install in subdirectories of the appropriate installation directory,
+such as @code{htmldir}.  As one example, if your package has multiple
+manuals, and you wish to install HTML documentation with many files
+(such as the ``split'' mode output by @code{makeinfo --html}), you'll
+certainly want to use subdirectories, or two nodes with the same name
+in different manuals will overwrite each other.
+
 @item uninstall
 Delete all the installed files---the copies that the @samp{install}
-target creates.
+and @samp{install-*} targets create.
 
 This rule should not modify the directories where compilation is done,
@@ -669 +756 @@
 @item clean
 
-Delete all files from the current directory that are normally created by
-building the program.  Don't delete the files that record the
-configuration.  Also preserve files that could be made by building, but
-normally aren't because the distribution comes with them.
+Delete all files in the current directory that are normally created by
+building the program.  Also delete files in other directories if they
+are created by this makefile.  However, don't delete the files that
+record the configuration.  Also preserve files that could be made by
+building, but normally aren't because the distribution comes with
+them.  There is no need to delete parent directories that were created
+with @samp{mkdir -p}, since they could have existed anyway.
 
 Delete @file{.dvi} files here if they are not part of the distribution.
 
 @item distclean
-Delete all files from the current directory that are created by
-configuring or building the program.  If you have unpacked the source
-and built the program without creating any other files, @samp{make
-distclean} should leave only the files that were in the distribution.
+Delete all files in the current directory (or created by this
+makefile) that are created by configuring or building the program.  If
+you have unpacked the source and built the program without creating
+any other files, @samp{make distclean} should leave only the files
+that were in the distribution.  However, there is no need to delete
+parent directories that were created with @samp{mkdir -p}, since they
+could have existed anyway.
 
 @item mostlyclean
@@ -689 +782 @@
 
 @item maintainer-clean
-Delete almost everything from the current directory that can be
-reconstructed with this Makefile.  This typically includes everything
-deleted by @code{distclean}, plus more: C source files produced by
-Bison, tags tables, Info files, and so on.
+Delete almost everything that can be reconstructed with this Makefile.
+This typically includes everything deleted by @code{distclean}, plus
+more: C source files produced by Bison, tags tables, Info files, and
+so on.
 
 The reason we say ``almost everything'' is that running the command
-@samp{make maintainer-clean} should not delete @file{configure} even if
-@file{configure} can be remade using a rule in the Makefile.  More generally,
-@samp{make maintainer-clean} should not delete anything that needs to
-exist in order to run @file{configure} and then begin to build the
-program.  This is the only exception; @code{maintainer-clean} should
-delete everything else that can be rebuilt.
+@samp{make maintainer-clean} should not delete @file{configure} even
+if @file{configure} can be remade using a rule in the Makefile.  More
+generally, @samp{make maintainer-clean} should not delete anything
+that needs to exist in order to run @file{configure} and then begin to
+build the program.  Also, there is no need to delete parent
+directories that were created with @samp{mkdir -p}, since they could
+have existed anyway.  These are the only exceptions;
+@code{maintainer-clean} should delete everything else that can be
+rebuilt.
 
 The @samp{maintainer-clean} target is intended to be used by a maintainer of
@@ -744 +840 @@
 
 @item dvi
-Generate DVI files for all Texinfo documentation.
-For example:
+@itemx html
+@itemx pdf
+@itemx ps
+Generate documentation files in the given format, if possible.
+Here's an example rule for generating DVI files from Texinfo:
 
 @smallexample
@@ -760 +859 @@
 of formatting. @TeX{} is not distributed with Texinfo.}  Alternatively,
 write just the dependencies, and allow GNU @code{make} to provide the command.
+
+Here's another example, this one for generating HTML from Texinfo:
+
+@smallexample
+html: foo.html
+
+foo.html: foo.texi chap1.texi chap2.texi
+        $(TEXI2HTML) $(srcdir)/foo.texi
+@end smallexample
+
+@noindent
+Again, you would define the variable @code{TEXI2HTML} in the Makefile;
+for example, it might run @code{makeinfo --no-split --html}
+(@command{makeinfo} is part of the Texinfo distribution).
 
 @item dist
@@ -933 +1046 @@
 Programs to build binary packages work by extracting the
 pre-installation and post-installation commands.  Here is one way of
-extracting the pre-installation commands:
-
-@smallexample
-make -n install -o all \
+extracting the pre-installation commands (the @option{-s} option to
+@command{make} is needed to silence messages about entering
+subdirectories):
+
+@smallexample
+make -s -n install -o all \
       PRE_INSTALL=pre-install \
       POST_INSTALL=post-install \
@@ -947 +1062 @@
 
 @smallexample
-$0 ~ /^\t[ \t]*(normal_install|post_install)[ \t]*$/ @{on = 0@}
+$0 ~ /^(normal-install|post-install)[ \t]*$/ @{on = 0@}
 on @{print $0@}
-$0 ~ /^\t[ \t]*pre_install[ \t]*$/ @{on = 1@}
-@end smallexample
-
-The resulting file of pre-installation commands is executed as a shell
-script as part of installing the binary package.
+$0 ~ /^pre-install[ \t]*$/ @{on = 1@}
+@end smallexample

vendor/gnumake/current/doc/make.info

@@ -1 @@
-This is make.info, produced by makeinfo version 4.6 from make.texi.
+This is make.info, produced by makeinfo version 4.8 from make.texi.
+
+   This file documents the GNU `make' utility, which determines
+automatically which pieces of a large program need to be recompiled,
+and issues the commands to recompile them.
+
+   This is Edition 0.70, last updated 1 April 2006, of `The GNU Make
+Manual', for GNU `make' version 3.81.
+
+   Copyright (C) 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996,
+1997, 1998, 1999, 2000, 2002, 2003, 2004, 2005, 2006 Free Software
+Foundation, Inc.
+
+     Permission is granted to copy, distribute and/or modify this
+     document under the terms of the GNU Free Documentation License,
+     Version 1.2 or any later version published by the Free Software
+     Foundation; with no Invariant Sections, with the Front-Cover Texts
+     being "A GNU Manual," and with the Back-Cover Texts as in (a)
+     below.  A copy of the license is included in the section entitled
+     "GNU Free Documentation License."
+
+     (a) The FSF's Back-Cover Text is: "You have freedom to copy and
+     modify this GNU Manual, like GNU software.  Copies published by
+     the Free Software Foundation raise funds for GNU development."
 
 INFO-DIR-SECTION GNU Packages
@@ -6 +29 @@
 END-INFO-DIR-ENTRY
 
-   This file documents the GNU Make utility, which determines
-automatically which pieces of a large program need to be recompiled,
-and issues the commands to recompile them.
-
-   This is Edition 0.61, last updated 02 May 2003, of `The GNU Make
-Manual', for `make', Version 3.81.
-
-   Copyright 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1997,
-1998, 1999, 2000, 2002, 2003, 2004 Free Software Foundation, Inc.
-
-   Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.1 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
-Texts.  A copy of the license is included in the section entitled "GNU
-Free Documentation License".
-
 
 Indirect:
-make.info-1: 997
-make.info-2: 300500
+make.info-1: 1297
+make.info-2: 301265
 
 Tag Table:
 (Indirect)
-Node: Top997
-Node: Overview13531
-Node: Preparing14535
-Node: Reading15507
-Node: Bugs16426
-Node: Introduction18248
-Node: Rule Introduction19832
-Node: Simple Makefile21568
-Node: How Make Works25189
-Node: Variables Simplify27677
-Node: make Deduces29880
-Node: Combine By Prerequisite31627
-Node: Cleanup32658
-Node: Makefiles34069
-Node: Makefile Contents34952
-Node: Makefile Names37899
-Node: Include39498
-Ref: Include-Footnote-143049
-Node: MAKEFILES Variable43183
-Node: MAKEFILE_LIST Variable44685
-Node: Special Variables46004
-Node: Remaking Makefiles46739
-Node: Overriding Makefiles50981
-Node: Reading Makefiles53031
-Node: Rules55558
-Node: Rule Example58226
-Node: Rule Syntax59075
-Node: Prerequisite Types61296
-Node: Wildcards63064
-Node: Wildcard Examples64747
-Node: Wildcard Pitfall65991
-Node: Wildcard Function67773
-Node: Directory Search69550
-Node: General Search70684
-Node: Selective Search72387
-Node: Search Algorithm75363
-Node: Commands/Search77870
-Node: Implicit/Search79205
-Node: Libraries/Search80137
-Node: Phony Targets82219
-Node: Force Targets87195
-Node: Empty Targets88232
-Node: Special Targets89519
-Node: Multiple Targets96215
-Node: Multiple Rules98075
-Node: Static Pattern100301
-Node: Static Usage100943
-Node: Static versus Implicit104664
-Node: Double-Colon106394
-Node: Automatic Prerequisites108041
-Node: Commands112295
-Node: Echoing113984
-Node: Execution115262
-Ref: Execution-Footnote-1119688
-Node: Parallel119834
-Node: Errors123417
-Node: Interrupts127053
-Node: Recursion128632
-Node: MAKE Variable130715
-Node: Variables/Recursion132966
-Node: Options/Recursion138111
-Node: -w Option143264
-Node: Sequences144247
-Node: Empty Commands147248
-Node: Using Variables148414
-Node: Reference151521
-Node: Flavors153077
-Node: Advanced158861
-Node: Substitution Refs159358
-Node: Computed Names160904
-Node: Values165471
-Node: Setting166376
-Node: Appending168404
-Node: Override Directive172319
-Node: Defining173695
-Node: Environment176151
-Node: Target-specific178423
-Node: Pattern-specific181380
-Node: Conditionals182772
-Node: Conditional Example183478
-Node: Conditional Syntax186062
-Node: Testing Flags190930
-Node: Functions192024
-Node: Syntax of Functions193366
-Node: Text Functions195557
-Node: File Name Functions203707
-Node: Foreach Function208146
-Node: If Function211346
-Node: Call Function212614
-Node: Value Function215496
-Node: Eval Function216930
-Node: Origin Function219236
-Node: Shell Function222445
-Node: Make Control Functions224026
-Node: Running225456
-Node: Makefile Arguments227441
-Node: Goals228149
-Node: Instead of Execution232704
-Node: Avoiding Compilation235982
-Node: Overriding237949
-Node: Testing240239
-Node: Options Summary242116
-Node: Implicit Rules251547
-Node: Using Implicit253691
-Node: Catalogue of Rules257220
-Node: Implicit Variables266203
-Node: Chained Rules270429
-Node: Pattern Rules274428
-Node: Pattern Intro275954
-Node: Pattern Examples278802
-Node: Automatic Variables280597
-Node: Pattern Match288760
-Node: Match-Anything Rules290381
-Node: Canceling Rules294242
-Node: Last Resort294944
-Node: Suffix Rules296781
-Node: Implicit Rule Search300500
-Node: Archives304009
-Node: Archive Members304701
-Node: Archive Update306297
-Node: Archive Symbols308201
-Node: Archive Pitfalls309421
-Node: Archive Suffix Rules310134
-Node: Features311671
-Node: Missing320218
-Node: Makefile Conventions323948
-Node: Makefile Basics324728
-Node: Utilities in Makefiles327885
-Node: Command Variables330013
-Node: Directory Variables333573
-Node: Standard Targets344450
-Ref: Standard Targets-Footnote-1355704
-Node: Install Command Categories355804
-Node: Quick Reference360369
-Node: Error Messages370113
-Node: Complex Makefile377782
-Node: GNU Free Documentation License386462
-Node: Concept Index406354
-Node: Name Index451260
+Node: Top1297
+Node: Overview14702
+Node: Preparing15712
+Node: Reading16684
+Node: Bugs17611
+Node: Introduction19441
+Node: Rule Introduction21033
+Node: Simple Makefile22777
+Node: How Make Works26406
+Node: Variables Simplify29061
+Node: make Deduces31267
+Node: Combine By Prerequisite33007
+Node: Cleanup34036
+Node: Makefiles35455
+Node: Makefile Contents36421
+Node: Makefile Names39376
+Node: Include40987
+Ref: Include-Footnote-144619
+Node: MAKEFILES Variable44753
+Node: MAKEFILE_LIST Variable46263
+Node: Special Variables47531
+Node: Remaking Makefiles51038
+Node: Overriding Makefiles55287
+Node: Reading Makefiles57340
+Node: Secondary Expansion60244
+Node: Rules67678
+Node: Rule Example70350
+Node: Rule Syntax71207
+Node: Prerequisite Types73710
+Node: Wildcards75486
+Node: Wildcard Examples77204
+Node: Wildcard Pitfall78460
+Node: Wildcard Function80249
+Node: Directory Search82033
+Node: General Search83175
+Node: Selective Search84890
+Node: Search Algorithm87878
+Node: Commands/Search90397
+Node: Implicit/Search91743
+Node: Libraries/Search92687
+Node: Phony Targets94779
+Node: Force Targets99865
+Node: Empty Targets100910
+Node: Special Targets102208
+Node: Multiple Targets109382
+Node: Multiple Rules111257
+Node: Static Pattern113493
+Node: Static Usage114145
+Node: Static versus Implicit117866
+Node: Double-Colon119610
+Node: Automatic Prerequisites121267
+Node: Commands125545
+Node: Command Syntax126753
+Node: Splitting Lines128778
+Node: Variables in Commands131759
+Node: Echoing133086
+Node: Execution134378
+Ref: Execution-Footnote-1135629
+Node: Choosing the Shell135775
+Node: Parallel139744
+Node: Errors143337
+Node: Interrupts146983
+Node: Recursion148570
+Node: MAKE Variable150664
+Node: Variables/Recursion152931
+Node: Options/Recursion158372
+Node: -w Option163537
+Node: Sequences164532
+Node: Empty Commands167544
+Node: Using Variables168718
+Node: Reference171831
+Node: Flavors173390
+Node: Advanced179128
+Node: Substitution Refs179633
+Node: Computed Names181186
+Node: Values185730
+Node: Setting186643
+Node: Appending188679
+Node: Override Directive192605
+Node: Defining193989
+Node: Environment196453
+Node: Target-specific198702
+Node: Pattern-specific201669
+Node: Conditionals203071
+Node: Conditional Example203781
+Node: Conditional Syntax206358
+Node: Testing Flags212083
+Node: Functions213185
+Node: Syntax of Functions214605
+Node: Text Functions216804
+Node: File Name Functions225375
+Node: Conditional Functions230597
+Node: Foreach Function232971
+Node: Call Function236183
+Node: Value Function239068
+Node: Eval Function240505
+Node: Origin Function242779
+Node: Flavor Function245997
+Node: Shell Function247063
+Node: Make Control Functions248697
+Node: Running250366
+Node: Makefile Arguments252355
+Node: Goals253071
+Node: Instead of Execution257812
+Node: Avoiding Compilation261098
+Node: Overriding263073
+Node: Testing265371
+Node: Options Summary267256
+Node: Implicit Rules277382
+Node: Using Implicit279530
+Node: Catalogue of Rules283069
+Node: Implicit Variables292419
+Node: Chained Rules297254
+Node: Pattern Rules301265
+Node: Pattern Intro302801
+Node: Pattern Examples305698
+Node: Automatic Variables307507
+Node: Pattern Match314878
+Node: Match-Anything Rules316514
+Node: Canceling Rules320389
+Node: Last Resort321105
+Node: Suffix Rules322952
+Node: Implicit Rule Search326681
+Node: Archives330200
+Node: Archive Members330898
+Node: Archive Update332511
+Node: Archive Symbols334425
+Node: Archive Pitfalls335659
+Node: Archive Suffix Rules336382
+Node: Features337929
+Node: Missing346484
+Node: Makefile Conventions350222
+Node: Makefile Basics351008
+Node: Utilities in Makefiles354175
+Node: Command Variables356313
+Node: Directory Variables359883
+Node: Standard Targets374023
+Ref: Standard Targets-Footnote-1387142
+Node: Install Command Categories387242
+Node: Quick Reference391768
+Node: Error Messages402464
+Node: Complex Makefile410154
+Node: GNU Free Documentation License418872
+Node: Concept Index441321
+Node: Name Index506510
 
 End Tag Table

vendor/gnumake/current/doc/make.info-1

@@ -1 @@
-This is make.info, produced by makeinfo version 4.6 from make.texi.
+This is make.info, produced by makeinfo version 4.8 from make.texi.
+
+   This file documents the GNU `make' utility, which determines
+automatically which pieces of a large program need to be recompiled,
+and issues the commands to recompile them.
+
+   This is Edition 0.70, last updated 1 April 2006, of `The GNU Make
+Manual', for GNU `make' version 3.81.
+
+   Copyright (C) 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996,
+1997, 1998, 1999, 2000, 2002, 2003, 2004, 2005, 2006 Free Software
+Foundation, Inc.
+
+     Permission is granted to copy, distribute and/or modify this
+     document under the terms of the GNU Free Documentation License,
+     Version 1.2 or any later version published by the Free Software
+     Foundation; with no Invariant Sections, with the Front-Cover Texts
+     being "A GNU Manual," and with the Back-Cover Texts as in (a)
+     below.  A copy of the license is included in the section entitled
+     "GNU Free Documentation License."
+
+     (a) The FSF's Back-Cover Text is: "You have freedom to copy and
+     modify this GNU Manual, like GNU software.  Copies published by
+     the Free Software Foundation raise funds for GNU development."
 
 INFO-DIR-SECTION GNU Packages
@@ -6 +29 @@
 END-INFO-DIR-ENTRY
 
-   This file documents the GNU Make utility, which determines
+
+File: make.info,  Node: Top,  Next: Overview,  Prev: (dir),  Up: (dir)
+
+GNU `make'
+**********
+
+This file documents the GNU `make' utility, which determines
 automatically which pieces of a large program need to be recompiled,
 and issues the commands to recompile them.
 
-   This is Edition 0.61, last updated 02 May 2003, of `The GNU Make
-Manual', for `make', Version 3.81.
-
-   Copyright 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1997,
-1998, 1999, 2000, 2002, 2003, 2004 Free Software Foundation, Inc.
-
-   Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.1 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
-Texts.  A copy of the license is included in the section entitled "GNU
-Free Documentation License".
-
-
-File: make.info,  Node: Top,  Next: Overview,  Prev: (dir),  Up: (dir)
-
-Make
-****
-
-The GNU `make' utility automatically determines which pieces of a large
-program need to be recompiled, and issues the commands to recompile
-them.
-
-   This edition of the `GNU Make Manual', last updated 02 May 2003,
-documents GNU `make' Version 3.81.
-
-   This manual describes `make' and contains the following chapters:
+   This is Edition 0.70, last updated 1 April 2006, of `The GNU Make
+Manual', for GNU `make' version 3.81.
+
+   Copyright (C) 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996,
+1997, 1998, 1999, 2000, 2002, 2003, 2004, 2005, 2006 Free Software
+Foundation, Inc.
+
+     Permission is granted to copy, distribute and/or modify this
+     document under the terms of the GNU Free Documentation License,
+     Version 1.2 or any later version published by the Free Software
+     Foundation; with no Invariant Sections, with the Front-Cover Texts
+     being "A GNU Manual," and with the Back-Cover Texts as in (a)
+     below.  A copy of the license is included in the section entitled
+     "GNU Free Documentation License."
+
+     (a) The FSF's Back-Cover Text is: "You have freedom to copy and
+     modify this GNU Manual, like GNU software.  Copies published by
+     the Free Software Foundation raise funds for GNU development."
 
 * Menu:
@@ -96 +116 @@
                                   with another makefile.
 * Reading Makefiles::           How makefiles are parsed.
+* Secondary Expansion::         How and when secondary expansion is performed.
 
 Writing Rules
@@ -106 +127 @@
 * Phony Targets::               Using a target that is not a real file's name.
 * Force Targets::               You can use a target without commands
-                                  or prerequisites to mark other
-                                  targets as phony.
+                                  or prerequisites to mark other targets
+                                  as phony.
 * Empty Targets::               When only the date matters and the
                                   files are empty.
@@ -147 +168 @@
 Writing the Commands in Rules
 
+* Command Syntax::              Command syntax features and pitfalls.
 * Echoing::                     How to control when commands are echoed.
 * Execution::                   How commands are executed.
@@ -155 +177 @@
 * Sequences::                   Defining canned sequences of commands.
 * Empty Commands::              Defining useful, do-nothing commands.
+
+Command Syntax
+
+* Splitting Lines::             Breaking long command lines for readability.
+* Variables in Commands::       Using `make' variables in commands.
+
+Command Execution
+
+* Choosing the Shell::          How `make' chooses the shell used
+                                  to run commands.
 
 Recursive Use of `make'
@@ -200 +232 @@
 * Text Functions::              General-purpose text manipulation functions.
 * File Name Functions::         Functions for manipulating file names.
+* Conditional Functions::       Functions that implement conditions.
 * Foreach Function::            Repeat some text with controlled variation.
-* If Function::                 Conditionally expand a value.
 * Call Function::               Expand a user-defined function.
 * Value Function::              Return the un-expanded value of a variable.
 * Eval Function::               Evaluate the arguments as makefile syntax.
 * Origin Function::             Find where a variable got its value.
+* Flavor Function::             Find out the flavor of a variable.
 * Shell Function::              Substitute the output of a shell command.
 * Make Control Functions::      Functions that control how make runs.
@@ -233 +266 @@
 * Chained Rules::               How to use a chain of implicit rules.
 * Pattern Rules::               How to define new implicit rules.
-* Last Resort::                 How to defining commands for rules
-                                  which cannot find any.
+* Last Resort::                 How to define commands for rules which
+                                  cannot find any.
 * Suffix Rules::                The old-fashioned style of implicit rule.
 * Implicit Rule Search::        The precise algorithm for applying
@@ -263 +296 @@
 * Archive Symbols::             How to update archive symbol directories.
 
-Makefile Conventions
-
-* Makefile Basics::             General Conventions for Makefiles
-* Utilities in Makefiles::      Utilities in Makefiles
-* Command Variables::           Variables for Specifying Commands
-* Directory Variables::         Variables for Installation Directories
-* Standard Targets::            Standard Targets for Users
-* Install Command Categories::  Three categories of commands in the `install'
-
-Copying This Manual
-
 
 File: make.info,  Node: Overview,  Next: Introduction,  Prev: Top,  Up: Top
 
-Overview of `make'
-******************
+1 Overview of `make'
+********************
 
 The `make' utility automatically determines which pieces of a large
@@ -287 +309 @@
 
    GNU `make' conforms to section 6.2 of `IEEE Standard 1003.2-1992'
-(POSIX.2).
+(POSIX.2).  
 
    Our examples show C programs, since they are most common, but you
@@ -329 +351 @@
 File: make.info,  Node: Reading,  Next: Bugs,  Prev: Preparing,  Up: Overview
 
-How to Read This Manual
-=======================
+1.1 How to Read This Manual
+===========================
 
 If you are new to `make', or are looking for a general introduction,
@@ -350 +372 @@
 File: make.info,  Node: Bugs,  Prev: Reading,  Up: Overview
 
-Problems and Bugs
-=================
+1.2 Problems and Bugs
+=====================
 
 If you have problems with GNU `make' or think you've found a bug,
@@ -393 +415 @@
 File: make.info,  Node: Introduction,  Next: Makefiles,  Prev: Overview,  Up: Top
 
-An Introduction to Makefiles
-****************************
+2 An Introduction to Makefiles
+******************************
 
 You need a file called a "makefile" to tell `make' what to do.  Most
-often, the makefile tells `make' how to compile and link a program.
+often, the makefile tells `make' how to compile and link a program.  
 
    In this chapter, we will discuss a simple makefile that describes
@@ -412 +434 @@
 Finally, if any source file has been recompiled, all the object files,
 whether newly made or saved from previous compilations, must be linked
-together to produce the new executable editor.
+together to produce the new executable editor.  
 
 * Menu:
@@ -427 +449 @@
 File: make.info,  Node: Rule Introduction,  Next: Simple Makefile,  Prev: Introduction,  Up: Introduction
 
-What a Rule Looks Like
-======================
+2.1 What a Rule Looks Like
+==========================
 
 A simple makefile consists of "rules" with the following shape:
@@ -470 +492 @@
 File: make.info,  Node: Simple Makefile,  Next: How Make Works,  Prev: Rule Introduction,  Up: Introduction
 
-A Simple Makefile
-=================
+2.2 A Simple Makefile
+=====================
 
 Here is a straightforward makefile that describes the way an executable
@@ -485 +507 @@
              cc -o edit main.o kbd.o command.o display.o \
                         insert.o search.o files.o utils.o
-     
+
      main.o : main.c defs.h
              cc -c main.c
@@ -507 +529 @@
 
 We split each long line into two lines using backslash-newline; this is
-like using one long line, but is easier to read.
+like using one long line, but is easier to read.  
 
    To use this makefile to create the executable file called `edit',
@@ -535 +557 @@
 prerequisites.  These shell commands say how to update the target file.
 A tab character must come at the beginning of every command line to
-distinguish commands lines from other lines in the makefile.  (Bear in
+distinguish command lines from other lines in the makefile.  (Bear in
 mind that `make' does not know anything about how the commands work.
 It is up to you to supply commands that will update the target file
 properly.  All `make' does is execute the commands in the rule you have
-specified when the target file needs to be updated.)
+specified when the target file needs to be updated.)  
 
    The target `clean' is not a file, but merely the name of an action.
@@ -550 +572 @@
 called "phony targets".  *Note Phony Targets::, for information about
 this kind of target.  *Note Errors in Commands: Errors, to see how to
-cause `make' to ignore errors from `rm' or any other command.
+cause `make' to ignore errors from `rm' or any other command.  
 
 
 File: make.info,  Node: How Make Works,  Next: Variables Simplify,  Prev: Simple Makefile,  Up: Introduction
 
-How `make' Processes a Makefile
-===============================
+2.3 How `make' Processes a Makefile
+===================================
 
 By default, `make' starts with the first target (not targets whose
 names start with `.').  This is called the "default goal".  ("Goals"
-are the targets that `make' strives ultimately to update.  *Note
-Arguments to Specify the Goals: Goals.)
+are the targets that `make' strives ultimately to update.    You can
+override this behavior using the command line (*note Arguments to
+Specify the Goals: Goals.) or with the `.DEFAULT_GOAL' special variable
+(*note Other Special Variables: Special Variables.).  
 
    In the simple example of the previous section, the default goal is to
@@ -596 +620 @@
 not exist, or if any of the object files are newer than it.  If an
 object file was just recompiled, it is now newer than `edit', so `edit'
-is relinked.
+is relinked.  
 
    Thus, if we change the file `insert.c' and run `make', `make' will
@@ -607 +631 @@
 File: make.info,  Node: Variables Simplify,  Next: make Deduces,  Prev: How Make Works,  Up: Introduction
 
-Variables Make Makefiles Simpler
-================================
+2.4 Variables Make Makefiles Simpler
+====================================
 
 In our example, we had to list all the object files twice in the rule
@@ -641 +665 @@
      objects = main.o kbd.o command.o display.o \
                insert.o search.o files.o utils.o
-     
+
      edit : $(objects)
              cc -o edit $(objects)
@@ -666 +690 @@
 File: make.info,  Node: make Deduces,  Next: Combine By Prerequisite,  Prev: Variables Simplify,  Up: Introduction
 
-Letting `make' Deduce the Commands
-==================================
+2.5 Letting `make' Deduce the Commands
+======================================
 
 It is not necessary to spell out the commands for compiling the
@@ -686 +710 @@
      objects = main.o kbd.o command.o display.o \
                insert.o search.o files.o utils.o
-     
+
      edit : $(objects)
              cc -o edit $(objects)
-     
+
      main.o : defs.h
      kbd.o : defs.h command.h
@@ -698 +722 @@
      files.o : defs.h buffer.h command.h
      utils.o : defs.h
-     
+
      .PHONY : clean
      clean :
@@ -713 +737 @@
 File: make.info,  Node: Combine By Prerequisite,  Next: Cleanup,  Prev: make Deduces,  Up: Introduction
 
-Another Style of Makefile
-=========================
+2.6 Another Style of Makefile
+=============================
 
 When the objects of a makefile are created only by implicit rules, an
@@ -723 +747 @@
      objects = main.o kbd.o command.o display.o \
                insert.o search.o files.o utils.o
-     
+
      edit : $(objects)
              cc -o edit $(objects)
-     
+
      $(objects) : defs.h
      kbd.o command.o files.o : command.h
@@ -742 +766 @@
 File: make.info,  Node: Cleanup,  Prev: Combine By Prerequisite,  Up: Introduction
 
-Rules for Cleaning the Directory
-================================
+2.7 Rules for Cleaning the Directory
+====================================
 
 Compiling a program is not the only thing you might want to write rules
@@ -781 +805 @@
 File: make.info,  Node: Makefiles,  Next: Rules,  Prev: Introduction,  Up: Top
 
-Writing Makefiles
-*****************
+3 Writing Makefiles
+*******************
 
 The information that tells `make' how to recompile a system comes from
@@ -799 +823 @@
                                   with another makefile.
 * Reading Makefiles::           How makefiles are parsed.
+* Secondary Expansion::         How and when secondary expansion is performed.
 
 
 File: make.info,  Node: Makefile Contents,  Next: Makefile Names,  Prev: Makefiles,  Up: Makefiles
 
-What Makefiles Contain
-======================
+3.1 What Makefiles Contain
+==========================
 
 Makefiles contain five kinds of things: "explicit rules", "implicit
@@ -864 +889 @@
 File: make.info,  Node: Makefile Names,  Next: Include,  Prev: Makefile Contents,  Up: Makefiles
 
-What Name to Give Your Makefile
-===============================
+3.2 What Name to Give Your Makefile
+===================================
 
 By default, when `make' looks for the makefile, it tries the following
-names, in order: `GNUmakefile', `makefile' and `Makefile'.
+names, in order: `GNUmakefile', `makefile' and `Makefile'.  
 
    Normally you should call your makefile either `makefile' or
@@ -891 +916 @@
 concatenated in the order specified.  The default makefile names
 `GNUmakefile', `makefile' and `Makefile' are not checked automatically
-if you specify `-f' or `--file'.
+if you specify `-f' or `--file'.  
 
 
 File: make.info,  Node: Include,  Next: MAKEFILES Variable,  Prev: Makefile Names,  Up: Makefiles
 
-Including Other Makefiles
-=========================
+3.3 Including Other Makefiles
+=============================
 
 The `include' directive tells `make' to suspend reading the current
@@ -905 +930 @@
      include FILENAMES...
 
-FILENAMES can contain shell file name patterns.
+FILENAMES can contain shell file name patterns.  If FILENAMES is empty,
+nothing is included and no error is printed.  
 
    Extra spaces are allowed and ignored at the beginning of the line,
@@ -942 +968 @@
 than that of somehow appending the prerequisites to the end of the main
 makefile as has been traditionally done with other versions of `make'.
-*Note Automatic Prerequisites::.
+*Note Automatic Prerequisites::.  
 
    If the specified name does not start with a slash, and the file is
@@ -980 +1006 @@
 File: make.info,  Node: MAKEFILES Variable,  Next: MAKEFILE_LIST Variable,  Prev: Include,  Up: Makefiles
 
-The Variable `MAKEFILES'
-========================
+3.4 The Variable `MAKEFILES'
+============================
 
 If the environment variable `MAKEFILES' is defined, `make' considers
@@ -1009 +1035 @@
 File: make.info,  Node: MAKEFILE_LIST Variable,  Next: Special Variables,  Prev: MAKEFILES Variable,  Up: Makefiles
 
-The Variable `MAKEFILE_LIST'
-============================
+3.5 The Variable `MAKEFILE_LIST'
+================================
 
 As `make' reads various makefiles, including any obtained from the
@@ -1025 +1051 @@
    If a makefile named `Makefile' has this content:
 
-     name1 := $(word $(words $(MAKEFILE_LIST)),$(MAKEFILE_LIST))
-     
+     name1 := $(lastword $(MAKEFILE_LIST))
+
      include inc.mk
-     
-     name2 := $(word $(words $(MAKEFILE_LIST)),$(MAKEFILE_LIST))
-     
+
+     name2 := $(lastword $(MAKEFILE_LIST))
+
      all:
              @echo name1 = $(name1)
@@ -1048 +1074 @@
 File: make.info,  Node: Special Variables,  Next: Remaking Makefiles,  Prev: MAKEFILE_LIST Variable,  Up: Makefiles
 
-Other Special Variables
-=======================
-
-GNU `make' also supports a special variable.  Note that any value you
-assign to this variable will be ignored; it will always return its
-special value.
-
-   The first special variable is `.VARIABLES'.  When expanded, the
-value consists of a list of the _names_ of all global variables defined
-in all makefiles read up until that point.  This includes variables
-which have empty values, as well as built-in variables (*note Variables
-Used by Implicit Rules: Implicit Variables.), but does not include any
-variables which are only defined in a target-specific context.
+3.6 Other Special Variables
+===========================
+
+GNU `make' also supports other special variables.  Unless otherwise
+documented here, these values lose their special properties if they are
+set by a makefile or on the command line.
+
+`.DEFAULT_GOAL'
+     Sets the default goal to be used if no targets were specified on
+     the command line (*note Arguments to Specify the Goals: Goals.).
+     The `.DEFAULT_GOAL' variable allows you to discover the current
+     default goal, restart the default goal selection algorithm by
+     clearing its value, or to explicitly set the default goal.  The
+     following example illustrates these cases:
+
+          # Query the default goal.
+          ifeq ($(.DEFAULT_GOAL),)
+            $(warning no default goal is set)
+          endif
+
+          .PHONY: foo
+          foo: ; @echo $@
+
+          $(warning default goal is $(.DEFAULT_GOAL))
+
+          # Reset the default goal.
+          .DEFAULT_GOAL :=
+
+          .PHONY: bar
+          bar: ; @echo $@
+
+          $(warning default goal is $(.DEFAULT_GOAL))
+
+          # Set our own.
+          .DEFAULT_GOAL := foo
+
+     This makefile prints:
+
+          no default goal is set
+          default goal is foo
+          default goal is bar
+          foo
+
+     Note that assigning more than one target name to `.DEFAULT_GOAL' is
+     illegal and will result in an error.
+
+`MAKE_RESTARTS'
+     This variable is set only if this instance of `make' has restarted
+     (*note How Makefiles Are Remade: Remaking Makefiles.): it will
+     contain the number of times this instance has restarted.  Note
+     this is not the same as recursion (counted by the `MAKELEVEL'
+     variable).  You should not set, modify, or export this variable.
+
+`.VARIABLES'
+     Expands to a list of the _names_ of all global variables defined
+     so far.  This includes variables which have empty values, as well
+     as built-in variables (*note Variables Used by Implicit Rules:
+     Implicit Variables.), but does not include any variables which are
+     only defined in a target-specific context.  Note that any value
+     you assign to this variable will be ignored; it will always return
+     its special value.
+
+`.FEATURES'
+     Expands to a list of special features supported by this version of
+     `make'.  Possible values include:
+
+    `archives'
+          Supports `ar' (archive) files using special filename syntax.
+          *Note Using `make' to Update Archive Files: Archives.
+
+    `check-symlink'
+          Supports the `-L' (`--check-symlink-times') flag.  *Note
+          Summary of Options: Options Summary.
+
+    `else-if'
+          Supports "else if" non-nested conditionals.  *Note Syntax of
+          Conditionals: Conditional Syntax.
+
+    `jobserver'
+          Supports "job server" enhanced parallel builds.  *Note
+          Parallel Execution: Parallel.
+
+    `second-expansion'
+          Supports secondary expansion of prerequisite lists.
+
+    `order-only'
+          Supports order-only prerequisites.  *Note Types of
+          Prerequisites: Prerequisite Types.
+
+    `target-specific'
+          Supports target-specific and pattern-specific variable
+          assignments.  *Note Target-specific Variable Values:
+          Target-specific.
+
+
+`.INCLUDE_DIRS'
+     Expands to a list of directories that `make' searches for included
+     makefiles (*note Including Other Makefiles: Include.).
+
 
 
 File: make.info,  Node: Remaking Makefiles,  Next: Overriding Makefiles,  Prev: Special Variables,  Up: Makefiles
 
-How Makefiles Are Remade
-========================
+3.7 How Makefiles Are Remade
+============================
 
 Sometimes makefiles can be remade from other files, such as RCS or SCCS
@@ -1103 +1215 @@
    If you do not specify any makefiles to be read with `-f' or `--file'
 options, `make' will try the default makefile names; *note What Name to
-Give Your Makefile: Makefile Names..  Unlike makefiles explicitly
+Give Your Makefile: Makefile Names.  Unlike makefiles explicitly
 requested with `-f' or `--file' options, `make' is not certain that
 these makefiles should exist.  However, if a default makefile does not
@@ -1143 +1255 @@
 File: make.info,  Node: Overriding Makefiles,  Next: Reading Makefiles,  Prev: Remaking Makefiles,  Up: Makefiles
 
-Overriding Part of Another Makefile
-===================================
+3.8 Overriding Part of Another Makefile
+=======================================
 
 Sometimes it is useful to have a makefile that is mostly just like
@@ -1164 +1276 @@
      foo:
              frobnicate > foo
-     
+
      %: force
              @$(MAKE) -f Makefile $@
@@ -1186 +1298 @@
 
 
-File: make.info,  Node: Reading Makefiles,  Prev: Overriding Makefiles,  Up: Makefiles
-
-How `make' Reads a Makefile
-===========================
+File: make.info,  Node: Reading Makefiles,  Next: Secondary Expansion,  Prev: Overriding Makefiles,  Up: Makefiles
+
+3.9 How `make' Reads a Makefile
+===============================
 
 GNU `make' does its work in two distinct phases.  During the first
@@ -1224 +1336 @@
      IMMEDIATE := IMMEDIATE
      IMMEDIATE += DEFERRED or IMMEDIATE
-     
+
      define IMMEDIATE
        DEFERRED
@@ -1238 +1350 @@
 All instances of conditional syntax are parsed immediately, in their
 entirety; this includes the `ifdef', `ifeq', `ifndef', and `ifneq'
-forms.
+forms.  Of course this means that automatic variables cannot be used in
+conditional statements, as automatic variables are not set until the
+command script for that rule is invoked.  If you need to use automatic
+variables in a conditional you _must_ use shell conditional syntax, in
+your command script proper, for these tests, not `make' conditionals.
 
 Rule Definition
@@ -1254 +1370 @@
 
 
+File: make.info,  Node: Secondary Expansion,  Prev: Reading Makefiles,  Up: Makefiles
+
+3.10 Secondary Expansion
+========================
+
+In the previous section we learned that GNU `make' works in two
+distinct phases: a read-in phase and a target-update phase (*note How
+`make' Reads a Makefile: Reading Makefiles.).  GNU make also has the
+ability to enable a _second expansion_ of the prerequisites (only) for
+some or all targets defined in the makefile.  In order for this second
+expansion to occur, the special target `.SECONDEXPANSION' must be
+defined before the first prerequisite list that makes use of this
+feature.
+
+   If that special target is defined then in between the two phases
+mentioned above, right at the end of the read-in phase, all the
+prerequisites of the targets defined after the special target are
+expanded a _second time_.  In most circumstances this secondary
+expansion will have no effect, since all variable and function
+references will have been expanded during the initial parsing of the
+makefiles.  In order to take advantage of the secondary expansion phase
+of the parser, then, it's necessary to _escape_ the variable or
+function reference in the makefile.  In this case the first expansion
+merely un-escapes the reference but doesn't expand it, and expansion is
+left to the secondary expansion phase.  For example, consider this
+makefile:
+
+     .SECONDEXPANSION:
+     ONEVAR = onefile
+     TWOVAR = twofile
+     myfile: $(ONEVAR) $$(TWOVAR)
+
+   After the first expansion phase the prerequisites list of the
+`myfile' target will be `onefile' and `$(TWOVAR)'; the first
+(unescaped) variable reference to ONEVAR is expanded, while the second
+(escaped) variable reference is simply unescaped, without being
+recognized as a variable reference.  Now during the secondary expansion
+the first word is expanded again but since it contains no variable or
+function references it remains the static value `onefile', while the
+second word is now a normal reference to the variable TWOVAR, which is
+expanded to the value `twofile'.  The final result is that there are
+two prerequisites, `onefile' and `twofile'.
+
+   Obviously, this is not a very interesting case since the same result
+could more easily have been achieved simply by having both variables
+appear, unescaped, in the prerequisites list.  One difference becomes
+apparent if the variables are reset; consider this example:
+
+     .SECONDEXPANSION:
+     AVAR = top
+     onefile: $(AVAR)
+     twofile: $$(AVAR)
+     AVAR = bottom
+
+   Here the prerequisite of `onefile' will be expanded immediately, and
+resolve to the value `top', while the prerequisite of `twofile' will
+not be full expanded until the secondary expansion and yield a value of
+`bottom'.
+
+   This is marginally more exciting, but the true power of this feature
+only becomes apparent when you discover that secondary expansions
+always take place within the scope of the automatic variables for that
+target.  This means that you can use variables such as `$@', `$*', etc.
+during the second expansion and they will have their expected values,
+just as in the command script.  All you have to do is defer the
+expansion by escaping the `$'.  Also, secondary expansion occurs for
+both explicit and implicit (pattern) rules.  Knowing this, the possible
+uses for this feature increase dramatically.  For example:
+
+     .SECONDEXPANSION:
+     main_OBJS := main.o try.o test.o
+     lib_OBJS := lib.o api.o
+
+     main lib: $$($$@_OBJS)
+
+   Here, after the initial expansion the prerequisites of both the
+`main' and `lib' targets will be `$($@_OBJS)'.  During the secondary
+expansion, the `$@' variable is set to the name of the target and so
+the expansion for the `main' target will yield `$(main_OBJS)', or
+`main.o try.o test.o', while the secondary expansion for the `lib'
+target will yield `$(lib_OBJS)', or `lib.o api.o'.
+
+   You can also mix functions here, as long as they are properly
+escaped:
+
+     main_SRCS := main.c try.c test.c
+     lib_SRCS := lib.c api.c
+
+     .SECONDEXPANSION:
+     main lib: $$(patsubst %.c,%.o,$$($$@_SRCS))
+
+   This version allows users to specify source files rather than object
+files, but gives the same resulting prerequisites list as the previous
+example.
+
+   Evaluation of automatic variables during the secondary expansion
+phase, especially of the target name variable `$$@', behaves similarly
+to evaluation within command scripts.  However, there are some subtle
+differences and "corner cases" which come into play for the different
+types of rule definitions that `make' understands.  The subtleties of
+using the different automatic variables are described below.
+
+Secondary Expansion of Explicit Rules
+-------------------------------------
+
+During the secondary expansion of explicit rules, `$$@' and `$$%'
+evaluate, respectively, to the file name of the target and, when the
+target is an archive member, the target member name.  The `$$<'
+variable evaluates to the first prerequisite in the first rule for this
+target.  `$$^' and `$$+' evaluate to the list of all prerequisites of
+rules _that have already appeared_ for the same target (`$$+' with
+repetitions and `$$^' without).  The following example will help
+illustrate these behaviors:
+
+     .SECONDEXPANSION:
+
+     foo: foo.1 bar.1 $$< $$^ $$+    # line #1
+
+     foo: foo.2 bar.2 $$< $$^ $$+    # line #2
+
+     foo: foo.3 bar.3 $$< $$^ $$+    # line #3
+
+   In the first prerequisite list, all three variables (`$$<', `$$^',
+and `$$+') expand to the empty string.  In the second, they will have
+values `foo.1', `foo.1 bar.1', and `foo.1 bar.1' respectively.  In the
+third they will have values `foo.1', `foo.1 bar.1 foo.2 bar.2', and
+`foo.1 bar.1 foo.2 bar.2' respectively.
+
+   Rules undergo secondary expansion in makefile order, except that the
+rule with the command script is always evaluated last.
+
+   The variables `$$?' and `$$*' are not available and expand to the
+empty string.
+
+Secondary Expansion of Static Pattern Rules
+-------------------------------------------
+
+Rules for secondary expansion of static pattern rules are identical to
+those for explicit rules, above, with one exception: for static pattern
+rules the `$$*' variable is set to the pattern stem.  As with explicit
+rules, `$$?' is not available and expands to the empty string.
+
+Secondary Expansion of Implicit Rules
+-------------------------------------
+
+As `make' searches for an implicit rule, it substitutes the stem and
+then performs secondary expansion for every rule with a matching target
+pattern.  The value of the automatic variables is derived in the same
+fashion as for static pattern rules.  As an example:
+
+     .SECONDEXPANSION:
+
+     foo: bar
+
+     foo foz: fo%: bo%
+
+     %oo: $$< $$^ $$+ $$*
+
+   When the implicit rule is tried for target `foo', `$$<' expands to
+`bar', `$$^' expands to `bar boo', `$$+' also expands to `bar boo', and
+`$$*' expands to `f'.
+
+   Note that the directory prefix (D), as described in *Note Implicit
+Rule Search Algorithm: Implicit Rule Search, is appended (after
+expansion) to all the patterns in the prerequisites list.  As an
+example:
+
+     .SECONDEXPANSION:
+
+     /tmp/foo.o:
+
+     %.o: $$(addsuffix /%.c,foo bar) foo.h
+
+   The prerequisite list after the secondary expansion and directory
+prefix reconstruction will be `/tmp/foo/foo.c /tmp/var/bar/foo.c
+foo.h'.  If you are not interested in this reconstruction, you can use
+`$$*' instead of `%' in the prerequisites list.
+
+
 File: make.info,  Node: Rules,  Next: Commands,  Prev: Makefiles,  Up: Top
 
-Writing Rules
-*************
+4 Writing Rules
+***************
 
 A "rule" appears in the makefile and says when and how to remake
@@ -1288 +1583 @@
 * Phony Targets::               Using a target that is not a real file's name.
 * Force Targets::               You can use a target without commands
-                                  or prerequisites to mark other
-                                  targets as phony.
+                                  or prerequisites to mark other targets
+                                  as phony.
 * Empty Targets::               When only the date matters and the
                                   files are empty.
@@ -1306 +1601 @@
 File: make.info,  Node: Rule Example,  Next: Rule Syntax,  Prev: Rules,  Up: Rules
 
-Rule Example
-============
+4.1 Rule Example
+================
 
 Here is an example of a rule:
@@ -1332 +1627 @@
 File: make.info,  Node: Rule Syntax,  Next: Prerequisite Types,  Prev: Rule Example,  Up: Rules
 
-Rule Syntax
-===========
+4.2 Rule Syntax
+===============
 
 In general, a rule looks like this:
@@ -1358 +1653 @@
 appear on the line after the prerequisites, with a tab character, or may
 appear on the same line, with a semicolon.  Either way, the effect is
-the same.  *Note Writing the Commands in Rules: Commands.
-
-   Because dollar signs are used to start variable references, if you
-really want a dollar sign in a rule you must write two of them, `$$'
-(*note How to Use Variables: Using Variables.).  You may split a long
-line by inserting a backslash followed by a newline, but this is not
-required, as `make' places no limit on the length of a line in a
-makefile.
+the same.  There are other differences in the syntax of command lines.
+*Note Writing the Commands in Rules: Commands.
+
+   Because dollar signs are used to start `make' variable references,
+if you really want a dollar sign in a target or prerequisite you must
+write two of them, `$$' (*note How to Use Variables: Using Variables.).
+If you have enabled secondary expansion (*note Secondary Expansion::)
+and you want a literal dollar sign in the prerequisites lise, you must
+actually write _four_ dollar signs (`$$$$').
+
+   You may split a long line by inserting a backslash followed by a
+newline, but this is not required, as `make' places no limit on the
+length of a line in a makefile.
 
    A rule tells `make' two things: when the targets are out of date,
@@ -1387 +1687 @@
 File: make.info,  Node: Prerequisite Types,  Next: Wildcards,  Prev: Rule Syntax,  Up: Rules
 
-Types of Prerequisites
-======================
+4.3 Types of Prerequisites
+==========================
 
 There are actually two different types of prerequisites understood by
@@ -1423 +1723 @@
 File: make.info,  Node: Wildcards,  Next: Directory Search,  Prev: Prerequisite Types,  Up: Rules
 
-Using Wildcard Characters in File Names
-=======================================
+4.4 Using Wildcard Characters in File Names
+===========================================
 
 A single file name can specify many files using "wildcard characters".
@@ -1440 +1740 @@
 simulated by setting the environment variable HOME.
 
-   Wildcard expansion happens automatically in targets, in
-prerequisites, and in commands (where the shell does the expansion).
-In other contexts, wildcard expansion happens only if you request it
-explicitly with the `wildcard' function.
+   Wildcard expansion is performed by `make' automatically in targets
+and in prerequisites.  In commands the shell is responsible for
+wildcard expansion.  In other contexts, wildcard expansion happens only
+if you request it explicitly with the `wildcard' function.
 
    The special significance of a wildcard character can be turned off by
@@ -1459 +1759 @@
 File: make.info,  Node: Wildcard Examples,  Next: Wildcard Pitfall,  Prev: Wildcards,  Up: Wildcards
 
-Wildcard Examples
------------------
+4.4.1 Wildcard Examples
+-----------------------
 
 Wildcards can be used in the commands of a rule, where they are expanded
@@ -1499 +1799 @@
 File: make.info,  Node: Wildcard Pitfall,  Next: Wildcard Function,  Prev: Wildcard Examples,  Up: Wildcards
 
-Pitfalls of Using Wildcards
----------------------------
+4.4.2 Pitfalls of Using Wildcards
+---------------------------------
 
 Now here is an example of a naive way of using wildcard expansion, that
@@ -1508 +1808 @@
 
      objects = *.o
-     
+
      foo : $(objects)
              cc -o foo $(CFLAGS) $(objects)
@@ -1542 +1842 @@
 File: make.info,  Node: Wildcard Function,  Prev: Wildcard Pitfall,  Up: Wildcards
 
-The Function `wildcard'
------------------------
+4.4.3 The Function `wildcard'
+-----------------------------
 
 Wildcard expansion happens automatically in rules.  But wildcard
@@ -1578 +1878 @@
 
      objects := $(patsubst %.c,%.o,$(wildcard *.c))
-     
+
      foo : $(objects)
              cc -o foo $(objects)
@@ -1590 +1890 @@
 File: make.info,  Node: Directory Search,  Next: Phony Targets,  Prev: Wildcards,  Up: Rules
 
-Searching Directories for Prerequisites
-=======================================
+4.5 Searching Directories for Prerequisites
+===========================================
 
 For large systems, it is often desirable to put sources in a separate
@@ -1614 +1914 @@
 File: make.info,  Node: General Search,  Next: Selective Search,  Prev: Directory Search,  Up: Directory Search
 
-`VPATH': Search Path for All Prerequisites
-------------------------------------------
+4.5.1 `VPATH': Search Path for All Prerequisites
+------------------------------------------------
 
 The value of the `make' variable `VPATH' specifies a list of
@@ -1658 +1958 @@
 File: make.info,  Node: Selective Search,  Next: Search Algorithm,  Prev: General Search,  Up: Directory Search
 
-The `vpath' Directive
----------------------
+4.5.2 The `vpath' Directive
+---------------------------
 
 Similar to the `VPATH' variable, but more selective, is the `vpath'
@@ -1737 +2037 @@
 File: make.info,  Node: Search Algorithm,  Next: Commands/Search,  Prev: Selective Search,  Up: Directory Search
 
-How Directory Searches are Performed
-------------------------------------
+4.5.3 How Directory Searches are Performed
+------------------------------------------
 
 When a prerequisite is found through directory search, regardless of
@@ -1795 +2095 @@
 File: make.info,  Node: Commands/Search,  Next: Implicit/Search,  Prev: Search Algorithm,  Up: Directory Search
 
-Writing Shell Commands with Directory Search
---------------------------------------------
+4.5.4 Writing Shell Commands with Directory Search
+--------------------------------------------------
 
 When a prerequisite is found in another directory through directory
@@ -1816 +2116 @@
 compilation by implicit rules; we use it here for consistency so it will
 affect all C compilations uniformly; *note Variables Used by Implicit
-Rules: Implicit Variables..)
+Rules: Implicit Variables.)
 
    Often the prerequisites include header files as well, which you do
@@ -1829 +2129 @@
 File: make.info,  Node: Implicit/Search,  Next: Libraries/Search,  Prev: Commands/Search,  Up: Directory Search
 
-Directory Search and Implicit Rules
------------------------------------
+4.5.5 Directory Search and Implicit Rules
+-----------------------------------------
 
 The search through the directories specified in `VPATH' or with `vpath'
@@ -1850 +2150 @@
 File: make.info,  Node: Libraries/Search,  Prev: Implicit/Search,  Up: Directory Search
 
-Directory Search for Link Libraries
------------------------------------
+4.5.6 Directory Search for Link Libraries
+-----------------------------------------
 
 Directory search applies in a special way to libraries used with the
@@ -1889 +2189 @@
 word in the list will be used.
 
-   The default value for `.LIBPATTERNS' is "`lib%.so lib%.a'", which
+   The default value for `.LIBPATTERNS' is `lib%.so lib%.a', which
 provides the default behavior described above.
 
@@ -1898 +2198 @@
 File: make.info,  Node: Phony Targets,  Next: Force Targets,  Prev: Directory Search,  Up: Rules
 
-Phony Targets
-=============
+4.6 Phony Targets
+=================
 
 A phony target is one that is not really the name of a file.  It is
@@ -1915 +2215 @@
 Because the `rm' command does not create a file named `clean', probably
 no such file will ever exist.  Therefore, the `rm' command will be
-executed every time you say `make clean'.
+executed every time you say `make clean'.  
 
    The phony target will cease to work if anything ever does create a
@@ -1945 +2245 @@
    Another example of the usefulness of phony targets is in conjunction
 with recursive invocations of `make' (for more information, see *Note
-Recursive Use of `make': Recursion).  In this case the makefile will
+Recursive Use of `make': Recursion.).  In this case the makefile will
 often contain a variable which lists a number of subdirectories to be
 built.  One way to handle this is with one rule whose command is a
@@ -1951 +2251 @@
 
      SUBDIRS = foo bar baz
-     
+
      subdirs:
              for dir in $(SUBDIRS); do \
@@ -1963 +2263 @@
 it will do so even if `make' is invoked with the `-k' option, which is
 unfortunate.  Second, and perhaps more importantly, you cannot take
-advantage of the parallel build capabilities of make using this method,
-since there is only one rule.
+advantage of `make''s ability to build targets in parallel (*note
+Parallel Execution: Parallel.), since there is only one rule.
 
    By declaring the subdirectories as phony targets (you must do this as
@@ -1971 +2271 @@
 
      SUBDIRS = foo bar baz
-     
+
      .PHONY: subdirs $(SUBDIRS)
-     
+
      subdirs: $(SUBDIRS)
-     
+
      $(SUBDIRS):
              $(MAKE) -C $@
-     
+
      foo: baz
 
@@ -2002 +2302 @@
      all : prog1 prog2 prog3
      .PHONY : all
-     
+
      prog1 : prog1.o utils.o
              cc -o prog1 prog1.o utils.o
-     
+
      prog2 : prog2.o
              cc -o prog2 prog2.o
-     
+
      prog3 : prog3.o sort.o utils.o
              cc -o prog3 prog3.o sort.o utils.o
 
 Now you can say just `make' to remake all three programs, or specify as
-arguments the ones to remake (as in `make prog1 prog3').
+arguments the ones to remake (as in `make prog1 prog3').  Phoniness is
+not inherited: the prerequisites of a phony target are not themselves
+phony, unless explicitly declared to be so.
 
    When one phony target is a prerequisite of another, it serves as a
@@ -2020 +2322 @@
 
      .PHONY: cleanall cleanobj cleandiff
-     
+
      cleanall : cleanobj cleandiff
              rm program
-     
+
      cleanobj :
              rm *.o
-     
+
      cleandiff :
              rm *.diff
@@ -2033 +2335 @@
 File: make.info,  Node: Force Targets,  Next: Empty Targets,  Prev: Phony Targets,  Up: Rules
 
-Rules without Commands or Prerequisites
-=======================================
+4.7 Rules without Commands or Prerequisites
+===========================================
 
 If a rule has no prerequisites or commands, and the target of the rule
@@ -2062 +2364 @@
 File: make.info,  Node: Empty Targets,  Next: Special Targets,  Prev: Force Targets,  Up: Rules
 
-Empty Target Files to Record Events
-===================================
+4.8 Empty Target Files to Record Events
+=======================================
 
 The "empty target" is a variant of the phony target; it is used to hold
@@ -2084 +2386 @@
              lpr -p $?
              touch print
-
+   
 With this rule, `make print' will execute the `lpr' command if either
 source file has changed since the last `make print'.  The automatic
@@ -2093 +2395 @@
 File: make.info,  Node: Special Targets,  Next: Multiple Targets,  Prev: Empty Targets,  Up: Rules
 
-Special Built-in Target Names
-=============================
+4.9 Special Built-in Target Names
+=================================
 
 Certain names have special meanings if they appear as targets.
@@ -2147 +2449 @@
      intermediate).
 
+`.SECONDEXPANSION'
+     If `.SECONDEXPANSION' is mentioned as a target anywhere in the
+     makefile, then all prerequisite lists defined _after_ it appears
+     will be expanded a second time after all makefiles have been read
+     in.  *Note Secondary Expansion: Secondary Expansion.
+
+     The prerequisites of the special target `.SUFFIXES' are the list
+     of suffixes to be used in checking for suffix rules.  *Note
+     Old-Fashioned Suffix Rules: Suffix Rules.
+
 `.DELETE_ON_ERROR'
      If `.DELETE_ON_ERROR' is mentioned as a target anywhere in the
@@ -2233 +2545 @@
 File: make.info,  Node: Multiple Targets,  Next: Multiple Rules,  Prev: Special Targets,  Up: Rules
 
-Multiple Targets in a Rule
-==========================
+4.10 Multiple Targets in a Rule
+===============================
 
 A rule with multiple targets is equivalent to writing many rules, each
@@ -2258 +2570 @@
           bigoutput littleoutput : text.g
                   generate text.g -$(subst output,,$@) > $@
-
+     
      is equivalent to
 
@@ -2280 +2592 @@
 File: make.info,  Node: Multiple Rules,  Next: Static Pattern,  Prev: Multiple Targets,  Up: Rules
 
-Multiple Rules for One Target
-=============================
+4.11 Multiple Rules for One Target
+==================================
 
 One file can be the target of several rules.  All the prerequisites
@@ -2331 +2643 @@
 File: make.info,  Node: Static Pattern,  Next: Double-Colon,  Prev: Multiple Rules,  Up: Rules
 
-Static Pattern Rules
-====================
+4.12 Static Pattern Rules
+=========================
 
 "Static pattern rules" are rules which specify multiple targets and
@@ -2348 +2660 @@
 File: make.info,  Node: Static Usage,  Next: Static versus Implicit,  Prev: Static Pattern,  Up: Static Pattern
 
-Syntax of Static Pattern Rules
-------------------------------
+4.12.1 Syntax of Static Pattern Rules
+-------------------------------------
 
 Here is the syntax of a static pattern rule:
@@ -2397 +2709 @@
 
      objects = foo.o bar.o
-     
+
      all: $(objects)
-     
+
      $(objects): %.o: %.c
              $(CC) -c $(CFLAGS) $< -o $@
@@ -2414 +2726 @@
 
      files = foo.elc bar.o lose.o
-     
+
      $(filter %.o,$(files)): %.o: %.c
              $(CC) -c $(CFLAGS) $< -o $@
@@ -2426 +2738 @@
 from `foo.el'.
 
-   Another example shows how to use `$*' in static pattern rules:
+   Another example shows how to use `$*' in static pattern rules: 
 
      bigoutput littleoutput : %output : text.g
@@ -2437 +2749 @@
 File: make.info,  Node: Static versus Implicit,  Prev: Static Usage,  Up: Static Pattern
 
-Static Pattern Rules versus Implicit Rules
-------------------------------------------
+4.12.2 Static Pattern Rules versus Implicit Rules
+-------------------------------------------------
 
 A static pattern rule has much in common with an implicit rule defined
@@ -2474 +2786 @@
 File: make.info,  Node: Double-Colon,  Next: Automatic Prerequisites,  Prev: Static Pattern,  Up: Rules
 
-Double-Colon Rules
-==================
+4.13 Double-Colon Rules
+=======================
 
 "Double-colon" rules are rules written with `::' instead of `:' after
@@ -2511 +2823 @@
 File: make.info,  Node: Automatic Prerequisites,  Prev: Double-Colon,  Up: Rules
 
-Generating Prerequisites Automatically
-======================================
+4.14 Generating Prerequisites Automatically
+===========================================
 
 In the makefile for a program, many of the rules you need to write often
@@ -2524 +2836 @@
 would have to write dozens of such rules in your makefile.  And, you
 must always be very careful to update the makefile every time you add
-or remove an `#include'.
+or remove an `#include'.  
 
    To avoid this hassle, most modern C compilers can write these rules
@@ -2543 +2855 @@
 makefile, so it can never be considered an intermediate file by implicit
 rule search.  This means that `make' won't ever remove the file after
-using it; *note Chains of Implicit Rules: Chained Rules..
+using it; *note Chains of Implicit Rules: Chained Rules.
 
    With old `make' programs, it was traditional practice to use this
@@ -2567 +2879 @@
 
      %.d: %.c
-             
+             @set -e; rm -f $@; \
               $(CC) -M $(CPPFLAGS) $< > $@.$$$$; \
               sed 's,\($*\)\.o[ :]*,\1.o $@ : ,g' < $@.$$$$ > $@; \
@@ -2574 +2886 @@
 *Note Pattern Rules::, for information on defining pattern rules.  The
 `-e' flag to the shell causes it to exit immediately if the `$(CC)'
-command (or any other command) fails (exits with a nonzero status).
+command (or any other command) fails (exits with a nonzero status).  
 
    With the GNU C compiler, you may wish to use the `-MM' flag instead
@@ -2599 +2911 @@
 
      sources = foo.c bar.c
-     
+
      include $(sources:.c=.d)
 
@@ -2610 +2922 @@
 
    Note that the `.d' files contain target definitions; you should be
-sure to place the `include' directive _after_ the first, default target
+sure to place the `include' directive _after_ the first, default goal
 in your makefiles or run the risk of having a random object file become
-the default target.  *Note How Make Works::.
+the default goal.  *Note How Make Works::.
 
 
 File: make.info,  Node: Commands,  Next: Using Variables,  Prev: Rules,  Up: Top
 
-Writing the Commands in Rules
-*****************************
-
-The commands of a rule consist of shell command lines to be executed one
-by one.  Each command line must start with a tab, except that the first
-command line may be attached to the target-and-prerequisites line with a
-semicolon in between.  Blank lines and lines of just comments may appear
-among the command lines; they are ignored.  (But beware, an apparently
-"blank" line that begins with a tab is _not_ blank!  It is an empty
-command; *note Empty Commands::.)
+5 Writing the Commands in Rules
+*******************************
+
+The commands of a rule consist of one or more shell command lines to be
+executed, one at a time, in the order they appear.  Typically, the
+result of executing these commands is that the target of the rule is
+brought up to date.
 
    Users use many different shell programs, but commands in makefiles
@@ -2632 +2941 @@
 otherwise.  *Note Command Execution: Execution.
 
-   The shell that is in use determines whether comments can be written
-on command lines, and what syntax they use.  When the shell is
-`/bin/sh', a `#' starts a comment that extends to the end of the line.
-The `#' does not have to be at the beginning of a line.  Text on a line
-before a `#' is not part of the comment.
-
 * Menu:
 
+* Command Syntax::              Command syntax features and pitfalls.
 * Echoing::                     How to control when commands are echoed.
 * Execution::                   How commands are executed.
@@ -2650 +2954 @@
 
 
-File: make.info,  Node: Echoing,  Next: Execution,  Prev: Commands,  Up: Commands
-
-Command Echoing
-===============
+File: make.info,  Node: Command Syntax,  Next: Echoing,  Prev: Commands,  Up: Commands
+
+5.1 Command Syntax
+==================
+
+Makefiles have the unusual property that there are really two distinct
+syntaxes in one file.  Most of the makefile uses `make' syntax (*note
+Writing Makefiles: Makefiles.).  However, commands are meant to be
+interpreted by the shell and so they are written using shell syntax.
+The `make' program does not try to understand shell syntax: it performs
+only a very few specific translations on the content of the command
+before handing it to the shell.
+
+   Each command line must start with a tab, except that the first
+command line may be attached to the target-and-prerequisites line with a
+semicolon in between.  _Any_ line in the makefile that begins with a
+tab and appears in a "rule context" (that is, after a rule has been
+started until another rule or variable definition) will be considered a
+command line for that rule.  Blank lines and lines of just comments may
+appear among the command lines; they are ignored.
+
+   Some consequences of these rules include:
+
+   * A blank line that begins with a tab is not blank: it's an empty
+     command (*note Empty Commands::).
+
+   * A comment in a command line is not a `make' comment; it will be
+     passed to the shell as-is.  Whether the shell treats it as a
+     comment or not depends on your shell.
+
+   * A variable definition in a "rule context" which is indented by a
+     tab as the first character on the line, will be considered a
+     command line, not a `make' variable definition, and passed to the
+     shell.
+
+   * A conditional expression (`ifdef', `ifeq', etc. *note Syntax of
+     Conditionals: Conditional Syntax.) in a "rule context" which is
+     indented by a tab as the first character on the line, will be
+     considered a command line and be passed to the shell.
+
+
+* Menu:
+
+* Splitting Lines::             Breaking long command lines for readability.
+* Variables in Commands::       Using `make' variables in commands.
+
+
+File: make.info,  Node: Splitting Lines,  Next: Variables in Commands,  Prev: Command Syntax,  Up: Command Syntax
+
+5.1.1 Splitting Command Lines
+-----------------------------
+
+One of the few ways in which `make' does interpret command lines is
+checking for a backslash just before the newline.  As in normal
+makefile syntax, a single command can be split into multiple lines in
+the makefile by placing a backslash before each newline.  A sequence of
+lines like this is considered a single command, and one instance of the
+shell will be invoked to run it.
+
+   However, in contrast to how they are treated in other places in a
+makefile, backslash-newline pairs are _not_ removed from the command.
+Both the backslash and the newline characters are preserved and passed
+to the shell.  How the backslash-newline is interpreted depends on your
+shell.  If the first character of the next line after the
+backslash-newline is a tab, then that tab (and only that tab) is
+removed.  Whitespace is never added to the command.
+
+   For example, this makefile:
+
+     all :
+             @echo no\
+     space
+             @echo no\
+             space
+             @echo one \
+             space
+             @echo one\
+              space
+
+consists of four separate shell commands where the output is:
+
+     nospace
+     nospace
+     one space
+     one space
+
+   As a more complex example, this makefile:
+
+     all : ; @echo 'hello \
+             world' ; echo "hello \
+         world"
+
+will run one shell with a command script of:
+
+     echo 'hello \
+     world' ; echo "hello \
+         world"
+
+which, according to shell quoting rules, will yield the following
+output:
+
+     hello \
+     world
+     hello     world
+
+Notice how the backslash/newline pair was removed inside the string
+quoted with double quotes (`"..."'), but not from the string quoted
+with single quotes (`'...'').  This is the way the default shell
+(`/bin/sh') handles backslash/newline pairs.  If you specify a
+different shell in your makefiles it may treat them differently.
+
+   Sometimes you want to split a long line inside of single quotes, but
+you don't want the backslash-newline to appear in the quoted content.
+This is often the case when passing scripts to languages such as Perl,
+where extraneous backslashes inside the script can change its meaning
+or even be a syntax error.  One simple way of handling this is to place
+the quoted string, or even the entire command, into a `make' variable
+then use the variable in the command.  In this situation the newline
+quoting rules for makefiles will be used, and the backslash-newline
+will be removed.  If we rewrite our example above using this method:
+
+     HELLO = 'hello \
+     world'
+
+     all : ; @echo $(HELLO)
+
+we will get output like this:
+
+     hello world
+
+   If you like, you can also use target-specific variables (*note
+Target-specific Variable Values: Target-specific.) to obtain a tighter
+correspondence between the variable and the command that uses it.
+
+
+File: make.info,  Node: Variables in Commands,  Prev: Splitting Lines,  Up: Command Syntax
+
+5.1.2 Using Variables in Commands
+---------------------------------
+
+The other way in which `make' processes commands is by expanding any
+variable references in them (*note Basics of Variable References:
+Reference.).  This occurs after make has finished reading all the
+makefiles and the target is determined to be out of date; so, the
+commands for targets which are not rebuilt are never expanded.
+
+   Variable and function references in commands have identical syntax
+and semantics to references elsewhere in the makefile.  They also have
+the same quoting rules: if you want a dollar sign to appear in your
+command, you must double it (`$$').  For shells like the default shell,
+that use dollar signs to introduce variables, it's important to keep
+clear in your mind whether the variable you want to reference is a
+`make' variable (use a single dollar sign) or a shell variable (use two
+dollar signs).  For example:
+
+     LIST = one two three
+     all:
+             for i in $(LIST); do \
+                 echo $$i; \
+             done
+
+results in the following command being passed to the shell:
+
+     for i in one two three; do \
+         echo $i; \
+     done
+
+which generates the expected result:
+
+     one
+     two
+     three
+
+
+File: make.info,  Node: Echoing,  Next: Execution,  Prev: Command Syntax,  Up: Commands
+
+5.2 Command Echoing
+===================
 
 Normally `make' prints each command line before it is executed.  We
@@ -2682 +3160 @@
 File: make.info,  Node: Execution,  Next: Parallel,  Prev: Echoing,  Up: Commands
 
-Command Execution
-=================
+5.3 Command Execution
+=====================
 
 When it is time to execute commands to update a target, they are
-executed by making a new subshell for each line.  (In practice, `make'
-may take shortcuts that do not affect the results.)
-
-   *Please note:* this implies that shell commands such as `cd' that
-set variables local to each process will not affect the following
-command lines. (1)  If you want to use `cd' to affect the next command,
-put the two on a single line with a semicolon between them.  Then
-`make' will consider them a single command and pass them, together, to
-a shell which will execute them in sequence.  For example:
+executed by invoking a new subshell for each command line.  (In
+practice, `make' may take shortcuts that do not affect the results.)
+
+   *Please note:* this implies that setting shell variables and
+invoking shell commands such as `cd' that set a context local to each
+process will not affect the following command lines.(1)  If you want to
+use `cd' to affect the next statement, put both statements in a single
+command line.  Then `make' will invoke one shell to run the entire
+line, and the shell will execute the statements in sequence.  For
+example:
 
      foo : bar/lose
-             cd bar; gobble lose > ../foo
-
-   If you would like to split a single shell command into multiple
-lines of text, you must use a backslash at the end of all but the last
-subline.  Such a sequence of lines is combined into a single line, by
-deleting the backslash-newline sequences, before passing it to the
-shell.  Thus, the following is equivalent to the preceding example:
-
-     foo : bar/lose
-             cd bar;  \
-             gobble lose > ../foo
-
-   The program used as the shell is taken from the variable `SHELL'.
-By default, the program `/bin/sh' is used.
+             cd $(@D) && gobble $(@F) > ../$@
+
+Here we use the shell AND operator (`&&') so that if the `cd' command
+fails, the script will fail without trying to invoke the `gobble'
+command in the wrong directory, which could cause problems (in this
+case it would certainly cause `../foo' to be truncated, at least).
+
+* Menu:
+
+* Choosing the Shell::          How `make' chooses the shell used
+                                  to run commands.
+
+   ---------- Footnotes ----------
+
+   (1) On MS-DOS, the value of current working directory is *global*, so
+changing it _will_ affect the following command lines on those systems.
+
+
+File: make.info,  Node: Choosing the Shell,  Prev: Execution,  Up: Execution
+
+5.3.1 Choosing the Shell
+------------------------
+
+The program used as the shell is taken from the variable `SHELL'.  If
+this variable is not set in your makefile, the program `/bin/sh' is
+used as the shell.
+
+   Unlike most variables, the variable `SHELL' is never set from the
+environment.  This is because the `SHELL' environment variable is used
+to specify your personal choice of shell program for interactive use.
+It would be very bad for personal choices like this to affect the
+functioning of makefiles.  *Note Variables from the Environment:
+Environment.
+
+   Furthermore, when you do set `SHELL' in your makefile that value is
+_not_ exported in the environment to commands that `make' invokes.
+Instead, the value inherited from the user's environment, if any, is
+exported.  You can override this behavior by explicitly exporting
+`SHELL' (*note Communicating Variables to a Sub-`make':
+Variables/Recursion.), forcing it to be passed in the environment to
+commands.
+
+   However, on MS-DOS and MS-Windows the value of `SHELL' in the
+environment *is* used, since on those systems most users do not set
+this variable, and therefore it is most likely set specifically to be
+used by `make'.  On MS-DOS, if the setting of `SHELL' is not suitable
+for `make', you can set the variable `MAKESHELL' to the shell that
+`make' should use; if set it will be used as the shell instead of the
+value of `SHELL'.
+
+Choosing a Shell in DOS and Windows
+...................................
+
+Choosing a shell in MS-DOS and MS-Windows is much more complex than on
+other systems.
 
    On MS-DOS, if `SHELL' is not set, the value of the variable
@@ -2756 +3276 @@
 
    The effect of the above DOS-specific processing is that a Makefile
-that says `SHELL = /bin/sh' (as many Unix makefiles do), will work on
-MS-DOS unaltered if you have e.g. `sh.exe' installed in some directory
-along your `PATH'.
-
-   Unlike most variables, the variable `SHELL' is never set from the
-environment.  This is because the `SHELL' environment variable is used
-to specify your personal choice of shell program for interactive use.
-It would be very bad for personal choices like this to affect the
-functioning of makefiles.  *Note Variables from the Environment:
-Environment.  However, on MS-DOS and MS-Windows the value of `SHELL' in
-the environment *is* used, since on those systems most users do not set
-this variable, and therefore it is most likely set specifically to be
-used by `make'.  On MS-DOS, if the setting of `SHELL' is not suitable
-for `make', you can set the variable `MAKESHELL' to the shell that
-`make' should use; this will override the value of `SHELL'.
-
-   ---------- Footnotes ----------
-
-   (1) On MS-DOS, the value of current working directory is *global*,
-so changing it _will_ affect the following command lines on those
-systems.
+that contains `SHELL = /bin/sh' (as many Unix makefiles do), will work
+on MS-DOS unaltered if you have e.g. `sh.exe' installed in some
+directory along your `PATH'.
 
 
 File: make.info,  Node: Parallel,  Next: Errors,  Prev: Execution,  Up: Commands
 
-Parallel Execution
-==================
+5.4 Parallel Execution
+======================
 
 GNU `make' knows how to execute several commands at once.  Normally,
@@ -2808 +3310 @@
 streams of all but one running command.  This means that attempting to
 read from standard input will usually be a fatal error (a `Broken pipe'
-signal) for most child processes if there are several.
+signal) for most child processes if there are several.  
 
    It is unpredictable which command will have a valid standard input
@@ -2857 +3359 @@
 File: make.info,  Node: Errors,  Next: Interrupts,  Prev: Parallel,  Up: Commands
 
-Errors in Commands
-==================
+5.5 Errors in Commands
+======================
 
 After each shell command returns, `make' looks at its exit status.  If
@@ -2916 +3418 @@
 program as possible, perhaps to find several independent problems so
 that you can correct them all before the next attempt to compile.  This
-is why Emacs' `compile' command passes the `-k' flag by default.
+is why Emacs' `compile' command passes the `-k' flag by default.  
 
    Usually when a command fails, if it has changed the target file at
@@ -2933 +3435 @@
 File: make.info,  Node: Interrupts,  Next: Recursion,  Prev: Errors,  Up: Commands
 
-Interrupting or Killing `make'
-==============================
+5.6 Interrupting or Killing `make'
+==================================
 
 If `make' gets a fatal signal while a command is executing, it may
@@ -2964 +3466 @@
 File: make.info,  Node: Recursion,  Next: Sequences,  Prev: Interrupts,  Up: Commands
 
-Recursive Use of `make'
-=======================
+5.7 Recursive Use of `make'
+===========================
 
 Recursive use of `make' means using `make' as a command in a makefile.
@@ -2981 +3483 @@
      subsystem:
              $(MAKE) -C subdir
-
+   
    You can write recursive `make' commands just by copying this example,
 but there are many things to know about how they work and why, and about
@@ -3011 +3513 @@
 File: make.info,  Node: MAKE Variable,  Next: Variables/Recursion,  Prev: Recursion,  Up: Recursion
 
-How the `MAKE' Variable Works
------------------------------
+5.7.1 How the `MAKE' Variable Works
+-----------------------------------
 
 Recursive `make' commands should always use the variable `MAKE', not
@@ -3024 +3526 @@
 is `cd subdir && /bin/make'.  If you use a special version of `make' to
 run the top-level makefile, the same special version will be executed
-for recursive invocations.
+for recursive invocations.  
 
    As a special feature, using the variable `MAKE' in the commands of a
@@ -3042 +3544 @@
 file named `subsystem' and do nothing else.  What you really want it to
 do is run `cd subdir && make -t'; but that would require executing the
-command, and `-t' says not to execute commands.
+command, and `-t' says not to execute commands.  
 
    The special feature makes this do what you want: whenever a command
@@ -3056 +3558 @@
 File: make.info,  Node: Variables/Recursion,  Next: Options/Recursion,  Prev: MAKE Variable,  Up: Recursion
 
-Communicating Variables to a Sub-`make'
----------------------------------------
+5.7.2 Communicating Variables to a Sub-`make'
+---------------------------------------------
 
 Variable values of the top-level `make' can be passed to the sub-`make'
@@ -3076 +3578 @@
 characters other than letters, numbers, and underscores.
 
-   The special variables `SHELL' and `MAKEFLAGS' are always exported
-(unless you unexport them).  `MAKEFILES' is exported if you set it to
-anything.
+   The value of the `make' variable `SHELL' is not exported.  Instead,
+the value of the `SHELL' variable from the invoking environment is
+passed to the sub-`make'.  You can force `make' to export its value for
+`SHELL' by using the `export' directive, described below.  *Note
+Choosing the Shell::.
+
+   The special variable `MAKEFLAGS' is always exported (unless you
+unexport it).  `MAKEFILES' is exported if you set it to anything.
 
    `make' automatically passes down variable values that were defined
@@ -3153 +3660 @@
 `.EXPORT_ALL_VARIABLES' instead of using the `export' directive.  This
 will be ignored by old `make's, while the `export' directive will cause
-a syntax error.
+a syntax error.  
 
    Likewise, you can use `unexport' by itself to tell `make' _not_ to
@@ -3186 +3693 @@
 File: make.info,  Node: Options/Recursion,  Next: -w Option,  Prev: Variables/Recursion,  Up: Recursion
 
-Communicating Options to a Sub-`make'
--------------------------------------
+5.7.3 Communicating Options to a Sub-`make'
+-------------------------------------------
 
 Flags such as `-s' and `-k' are passed automatically to the sub-`make'
@@ -3291 +3798 @@
 File: make.info,  Node: -w Option,  Prev: Options/Recursion,  Up: Recursion
 
-The `--print-directory' Option
-------------------------------
+5.7.4 The `--print-directory' Option
+------------------------------------
 
 If you use several levels of recursive `make' invocations, the `-w' or
@@ -3317 +3824 @@
 File: make.info,  Node: Sequences,  Next: Empty Commands,  Prev: Recursion,  Up: Commands
 
-Defining Canned Command Sequences
-=================================
+5.8 Defining Canned Command Sequences
+=====================================
 
 When the same sequence of commands is useful in making various targets,
@@ -3332 +3839 @@
      mv y.tab.c $@
      endef
-
+   
 Here `run-yacc' is the name of the variable being defined; `endef'
 marks the end of the definition; the lines in between are the commands.
@@ -3392 +3899 @@
 File: make.info,  Node: Empty Commands,  Prev: Sequences,  Up: Commands
 
-Using Empty Commands
-====================
+5.9 Using Empty Commands
+========================
 
 It is sometimes useful to define commands which do nothing.  This is
@@ -3421 +3928 @@
 File: make.info,  Node: Using Variables,  Next: Conditionals,  Prev: Commands,  Up: Top
 
-How to Use Variables
-********************
+6 How to Use Variables
+**********************
 
 A "variable" is a name defined in a makefile to represent a string of
@@ -3428 +3935 @@
 explicit request into targets, prerequisites, commands, and other parts
 of the makefile.  (In some other versions of `make', variables are
-called "macros".)
+called "macros".)  
 
    Variables and functions in all parts of a makefile are expanded when
@@ -3483 +3990 @@
 File: make.info,  Node: Reference,  Next: Flavors,  Prev: Using Variables,  Up: Using Variables
 
-Basics of Variable References
-=============================
+6.1 Basics of Variable References
+=================================
 
 To substitute a variable's value, write a dollar sign followed by the
@@ -3500 +4007 @@
      program : $(objects)
              cc -o program $(objects)
-     
+
      $(objects) : defs.h
 
@@ -3523 +4030 @@
 File: make.info,  Node: Flavors,  Next: Advanced,  Prev: Reference,  Up: Using Variables
 
-The Two Flavors of Variables
-============================
+6.2 The Two Flavors of Variables
+================================
 
 There are two ways that a variable in GNU `make' can have a value; we
@@ -3544 +4051 @@
      bar = $(ugh)
      ugh = Huh?
-     
+
      all:;echo $(foo)
 
@@ -3564 +4071 @@
 
 because it will cause an infinite loop in the variable expansion.
-(Actually `make' detects the infinite loop and reports an error.)
+(Actually `make' detects the infinite loop and reports an error.)  
 
    Another disadvantage is that any functions (*note Functions for
@@ -3605 +4112 @@
 
      ifeq (0,${MAKELEVEL})
-     cur-dir   := $(shell pwd)
      whoami    := $(shell whoami)
      host-type := $(shell arch)
@@ -3615 +4121 @@
 
      ${subdirs}:
-           ${MAKE} cur-dir=${cur-dir}/$@ -C $@ all
+             ${MAKE} -C $@ all
 
    Simply expanded variables generally make complicated makefile
@@ -3669 +4175 @@
 File: make.info,  Node: Advanced,  Next: Values,  Prev: Flavors,  Up: Using Variables
 
-Advanced Features for Reference to Variables
-============================================
+6.3 Advanced Features for Reference to Variables
+================================================
 
 This section describes some advanced features you can use to reference
@@ -3684 +4190 @@
 File: make.info,  Node: Substitution Refs,  Next: Computed Names,  Prev: Advanced,  Up: Advanced
 
-Substitution References
------------------------
+6.3.1 Substitution References
+-----------------------------
 
 A "substitution reference" substitutes the value of a variable with
@@ -3717 +4223 @@
 
 For example:
-     
+
      foo := a.o b.o c.o
      bar := $(foo:%.o=%.c)
@@ -3726 +4232 @@
 File: make.info,  Node: Computed Names,  Prev: Substitution Refs,  Up: Advanced
 
-Computed Variable Names
------------------------
+6.3.2 Computed Variable Names
+-----------------------------
 
 Computed variable names are a complicated concept needed only for
@@ -3798 +4304 @@
      a_dirs := dira dirb
      1_dirs := dir1 dir2
-     
+
      a_files := filea fileb
      1_files := file1 file2
-     
+
      ifeq "$(use_a)" "yes"
      a1 := a
@@ -3807 +4313 @@
      a1 := 1
      endif
-     
+
      ifeq "$(use_dirs)" "yes"
      df := dirs
@@ -3813 +4319 @@
      df := files
      endif
-     
+
      dirs := $($(a1)_$(df))
 
@@ -3823 +4329 @@
      a_objects := a.o b.o c.o
      1_objects := 1.o 2.o 3.o
-     
+
      sources := $($(a1)_objects:.o=.c)
 
@@ -3839 +4345 @@
      func := strip
      endif
-     
+
      bar := a d b g q c
-     
+
      foo := $($(func) $(bar))
 
@@ -3869 +4375 @@
 File: make.info,  Node: Values,  Next: Setting,  Prev: Advanced,  Up: Using Variables
 
-How Variables Get Their Values
-==============================
+6.4 How Variables Get Their Values
+==================================
 
 Variables can get values in several different ways:
@@ -3894 +4400 @@
 File: make.info,  Node: Setting,  Next: Appending,  Prev: Values,  Up: Using Variables
 
-Setting Variables
-=================
+6.5 Setting Variables
+=====================
 
 To set a variable from the makefile, write a line starting with the
@@ -3947 +4453 @@
 File: make.info,  Node: Appending,  Next: Override Directive,  Prev: Setting,  Up: Using Variables
 
-Appending More Text to Variables
-================================
+6.6 Appending More Text to Variables
+====================================
 
 Often it is useful to add more text to the value of a variable already
@@ -3983 +4489 @@
 it a simply-expanded variable, `+=' adds to that simply-expanded
 definition, and expands the new text before appending it to the old
-value just as `:=' does (*note Setting Variables: Setting., for a full
-explanation of `:=').  In fact,
+value just as `:=' does (see *Note Setting Variables: Setting, for a
+full explanation of `:=').  In fact,
 
      variable := value
@@ -3990 +4496 @@
 
 is exactly equivalent to:
+
 
      variable := value
@@ -4022 +4529 @@
 The first line defines the `CFLAGS' variable with a reference to another
 variable, `includes'.  (`CFLAGS' is used by the rules for C
-compilation; *note Catalogue of Implicit Rules: Catalogue of Rules..)
+compilation; *note Catalogue of Implicit Rules: Catalogue of Rules.)
 Using `=' for the definition makes `CFLAGS' a recursively-expanded
 variable, meaning `$(includes) -O' is _not_ expanded when `make'
@@ -4044 +4551 @@
 File: make.info,  Node: Override Directive,  Next: Defining,  Prev: Appending,  Up: Using Variables
 
-The `override' Directive
-========================
+6.7 The `override' Directive
+============================
 
 If a variable has been set with a command argument (*note Overriding
@@ -4088 +4595 @@
 File: make.info,  Node: Defining,  Next: Environment,  Prev: Override Directive,  Up: Using Variables
 
-Defining Variables Verbatim
-===========================
+6.8 Defining Variables Verbatim
+===============================
 
 Another way to set the value of a variable is to use the `define'
@@ -4147 +4654 @@
 File: make.info,  Node: Environment,  Next: Target-specific,  Prev: Defining,  Up: Using Variables
 
-Variables from the Environment
-==============================
+6.9 Variables from the Environment
+==================================
 
 Variables in `make' can come from the environment in which `make' is
 run.  Every environment variable that `make' sees when it starts up is
-transformed into a `make' variable with the same name and value.  But
-an explicit assignment in the makefile, or with a command argument,
-overrides the environment.  (If the `-e' flag is specified, then values
-from the environment override assignments in the makefile.  *Note
-Summary of Options: Options Summary.  But this is not recommended
+transformed into a `make' variable with the same name and value.
+However, an explicit assignment in the makefile, or with a command
+argument, overrides the environment.  (If the `-e' flag is specified,
+then values from the environment override assignments in the makefile.
+*Note Summary of Options: Options Summary.  But this is not recommended
 practice.)
 
@@ -4163 +4670 @@
 you prefer.  This is safe for variables with standard or conventional
 meanings because you know that no makefile will use them for other
-things.  (But this is not totally reliable; some makefiles set `CFLAGS'
-explicitly and therefore are not affected by the value in the
+things.  (Note this is not totally reliable; some makefiles set
+`CFLAGS' explicitly and therefore are not affected by the value in the
 environment.)
 
-   When `make' is invoked recursively, variables defined in the outer
-invocation can be passed to inner invocations through the environment
-(*note Recursive Use of `make': Recursion.).  By default, only
-variables that came from the environment or the command line are passed
-to recursive invocations.  You can use the `export' directive to pass
-other variables.  *Note Communicating Variables to a Sub-`make':
-Variables/Recursion, for full details.
+   When `make' runs a command script, variables defined in the makefile
+are placed into the environment of that command.  This allows you to
+pass values to sub-`make' invocations (*note Recursive Use of `make':
+Recursion.).  By default, only variables that came from the environment
+or the command line are passed to recursive invocations.  You can use
+the `export' directive to pass other variables.  *Note Communicating
+Variables to a Sub-`make': Variables/Recursion, for full details.
 
    Other use of variables from the environment is not recommended.  It
@@ -4184 +4691 @@
 which is normally present in the environment to specify the user's
 choice of interactive shell.  It would be very undesirable for this
-choice to affect `make'.  So `make' ignores the environment value of
-`SHELL' (except on MS-DOS and MS-Windows, where `SHELL' is usually not
-set.  *Note Special handling of SHELL on MS-DOS: Execution.)
+choice to affect `make'; so, `make' handles the `SHELL' environment
+variable in a special way; see *Note Choosing the Shell::.
 
 
 File: make.info,  Node: Target-specific,  Next: Pattern-specific,  Prev: Environment,  Up: Using Variables
 
-Target-specific Variable Values
-===============================
+6.10 Target-specific Variable Values
+====================================
 
 Variable values in `make' are usually global; that is, they are the
@@ -4261 +4767 @@
 File: make.info,  Node: Pattern-specific,  Prev: Target-specific,  Up: Using Variables
 
-Pattern-specific Variable Values
-================================
+6.11 Pattern-specific Variable Values
+=====================================
 
 In addition to target-specific variable values (*note Target-specific
@@ -4299 +4805 @@
 File: make.info,  Node: Conditionals,  Next: Functions,  Prev: Using Variables,  Up: Top
 
-Conditional Parts of Makefiles
-******************************
+7 Conditional Parts of Makefiles
+********************************
 
 A "conditional" causes part of a makefile to be obeyed or ignored
@@ -4318 +4824 @@
 File: make.info,  Node: Conditional Example,  Next: Conditional Syntax,  Prev: Conditionals,  Up: Conditionals
 
-Example of a Conditional
-========================
+7.1 Example of a Conditional
+============================
 
 The following example of a conditional tells `make' to use one set of
@@ -4330 +4836 @@
      libs_for_gcc = -lgnu
      normal_libs =
-     
+
      foo: $(objects)
      ifeq ($(CC),gcc)
@@ -4380 +4886 @@
      libs_for_gcc = -lgnu
      normal_libs =
-     
+
      ifeq ($(CC),gcc)
        libs=$(libs_for_gcc)
@@ -4386 +4892 @@
        libs=$(normal_libs)
      endif
-     
+
      foo: $(objects)
              $(CC) -o foo $(objects) $(libs)
@@ -4393 +4899 @@
 File: make.info,  Node: Conditional Syntax,  Next: Testing Flags,  Prev: Conditional Example,  Up: Conditionals
 
-Syntax of Conditionals
-======================
+7.2 Syntax of Conditionals
+==========================
 
 The syntax of a simple conditional with no `else' is as follows:
@@ -4414 +4920 @@
      endif
 
-If the condition is true, TEXT-IF-TRUE is used; otherwise,
-TEXT-IF-FALSE is used instead.  The TEXT-IF-FALSE can be any number of
-lines of text.
+   or:
+
+     CONDITIONAL-DIRECTIVE
+     TEXT-IF-ONE-IS-TRUE
+     else CONDITIONAL-DIRECTIVE
+     TEXT-IF-TRUE
+     else
+     TEXT-IF-FALSE
+     endif
+
+There can be as many "`else' CONDITIONAL-DIRECTIVE" clauses as
+necessary.  Once a given condition is true, TEXT-IF-TRUE is used and no
+other clause is used; if no condition is true then TEXT-IF-FALSE is
+used.  The TEXT-IF-TRUE and TEXT-IF-FALSE can be any number of lines of
+text.
 
    The syntax of the CONDITIONAL-DIRECTIVE is the same whether the
-conditional is simple or complex.  There are four different directives
-that test different conditions.  Here is a table of them:
+conditional is simple or complex; after an `else' or not.  There are
+four different directives that test different conditions.  Here is a
+table of them:
 
 `ifeq (ARG1, ARG2)'
@@ -4456 +4975 @@
 
 `ifdef VARIABLE-NAME'
-     If the variable VARIABLE-NAME has a non-empty value, the
-     TEXT-IF-TRUE is effective; otherwise, the TEXT-IF-FALSE, if any,
-     is effective.  Variables that have never been defined have an
-     empty value.  The variable VARIABLE-NAME is itself expanded, so it
-     could be a variable or function that expands to the name of a
-     variable.
+     The `ifdef' form takes the _name_ of a variable as its argument,
+     not a reference to a variable.  The value of that variable has a
+     non-empty value, the TEXT-IF-TRUE is effective; otherwise, the
+     TEXT-IF-FALSE, if any, is effective.  Variables that have never
+     been defined have an empty value.  The text VARIABLE-NAME is
+     expanded, so it could be a variable or function that expands to
+     the name of a variable.  For example:
+
+          bar = true
+          foo = bar
+          ifdef $(foo)
+          frobozz = yes
+          endif
+
+     The variable reference `$(foo)' is expanded, yielding `bar', which
+     is considered to be the name of a variable.  The variable `bar' is
+     not expanded, but its value is examined to determine if it is
+     non-empty.
 
      Note that `ifdef' only tests whether a variable has a value.  It
@@ -4491 +5022 @@
      If the variable VARIABLE-NAME has an empty value, the TEXT-IF-TRUE
      is effective; otherwise, the TEXT-IF-FALSE, if any, is effective.
+     The rules for expansion and testing of VARIABLE-NAME are identical
+     to the `ifdef' directive.
 
    Extra spaces are allowed and ignored at the beginning of the
@@ -4525 +5058 @@
 File: make.info,  Node: Testing Flags,  Prev: Conditional Syntax,  Up: Conditionals
 
-Conditionals that Test Flags
-============================
+7.3 Conditionals that Test Flags
+================================
 
 You can write a conditional that tests `make' command flags such as
@@ -4556 +5089 @@
 File: make.info,  Node: Functions,  Next: Running,  Prev: Conditionals,  Up: Top
 
-Functions for Transforming Text
-*******************************
+8 Functions for Transforming Text
+*********************************
 
 "Functions" allow you to do text processing in the makefile to compute
@@ -4571 +5104 @@
 * Text Functions::              General-purpose text manipulation functions.
 * File Name Functions::         Functions for manipulating file names.
+* Conditional Functions::       Functions that implement conditions.
 * Foreach Function::            Repeat some text with controlled variation.
-* If Function::                 Conditionally expand a value.
 * Call Function::               Expand a user-defined function.
 * Value Function::              Return the un-expanded value of a variable.
 * Eval Function::               Evaluate the arguments as makefile syntax.
 * Origin Function::             Find where a variable got its value.
+* Flavor Function::             Find out the flavor of a variable.
 * Shell Function::              Substitute the output of a shell command.
 * Make Control Functions::      Functions that control how make runs.
@@ -4583 +5117 @@
 File: make.info,  Node: Syntax of Functions,  Next: Text Functions,  Prev: Functions,  Up: Functions
 
-Function Call Syntax
-====================
+8.1 Function Call Syntax
+========================
 
 A function call resembles a variable reference.  It looks like this:
@@ -4637 +5171 @@
 File: make.info,  Node: Text Functions,  Next: File Name Functions,  Prev: Syntax of Functions,  Up: Functions
 
-Functions for String Substitution and Analysis
-==============================================
+8.2 Functions for String Substitution and Analysis
+==================================================
 
 Here are some functions that operate on strings:
@@ -4803 +5337 @@
 `$(wordlist S,E,TEXT)'
      Returns the list of words in TEXT starting with word S and ending
-     with word E (inclusive).  The legitimate values of S and E start
-     from 1.  If S is bigger than the number of words in TEXT, the
-     value is empty.  If E is bigger than the number of words in TEXT,
-     words up to the end of TEXT are returned.  If S is greater than E,
-     nothing is returned.  For example,
+     with word E (inclusive).  The legitimate values of S start from 1;
+     E may start from 0.  If S is bigger than the number of words in
+     TEXT, the value is empty.  If E is bigger than the number of words
+     in TEXT, words up to the end of TEXT are returned.  If S is
+     greater than E, nothing is returned.  For example,
 
           $(wordlist 2, 3, foo bar baz)
@@ -4829 +5363 @@
      same as `$(word 1,TEXT)', the `firstword' function is retained for
      its simplicity.
+
+`$(lastword NAMES...)'
+     The argument NAMES is regarded as a series of names, separated by
+     whitespace.  The value is the last name in the series.
+
+     For example,
+
+          $(lastword foo bar)
+
+     produces the result `bar'.  Although `$(lastword TEXT)' is the
+     same as `$(word $(words TEXT),TEXT)', the `lastword' function was
+     added for its simplicity and better performance.
 
    Here is a realistic example of the use of `subst' and `patsubst'.
@@ -4857 +5403 @@
 
 
-File: make.info,  Node: File Name Functions,  Next: Foreach Function,  Prev: Text Functions,  Up: Functions
-
-Functions for File Names
-========================
+File: make.info,  Node: File Name Functions,  Next: Conditional Functions,  Prev: Text Functions,  Up: Functions
+
+8.3 Functions for File Names
+============================
 
 Several of the built-in expansion functions relate specifically to
@@ -4969 +5515 @@
      File Names: Wildcards.
 
-
-File: make.info,  Node: Foreach Function,  Next: If Function,  Prev: File Name Functions,  Up: Functions
-
-The `foreach' Function
-======================
+`$(realpath NAMES...)'
+     For each file name in NAMES return the canonical absolute name.  A
+     canonical name does not contain any `.' or `..' components, nor
+     any repeated path separators (`/') or symlinks.  In case of a
+     failure the empty string is returned.  Consult the `realpath(3)'
+     documentation for a list of possible failure causes.
+
+`$(abspath NAMES...)'
+     For each file name in NAMES return an absolute name that does not
+     contain any `.' or `..' components, nor any repeated path
+     separators (`/').  Note that, in contrast to `realpath' function,
+     `abspath' does not resolve symlinks and does not require the file
+     names to refer to an existing file or directory.  Use the
+     `wildcard' function to test for existence.
+
+
+File: make.info,  Node: Conditional Functions,  Next: Foreach Function,  Prev: File Name Functions,  Up: Functions
+
+8.4 Functions for Conditionals
+==============================
+
+There are three functions that provide conditional expansion.  A key
+aspect of these functions is that not all of the arguments are expanded
+initially.  Only those arguments which need to be expanded, will be
+expanded.
+
+`$(if CONDITION,THEN-PART[,ELSE-PART])'
+     The `if' function provides support for conditional expansion in a
+     functional context (as opposed to the GNU `make' makefile
+     conditionals such as `ifeq' (*note Syntax of Conditionals:
+     Conditional Syntax.).
+
+     The first argument, CONDITION, first has all preceding and
+     trailing whitespace stripped, then is expanded.  If it expands to
+     any non-empty string, then the condition is considered to be true.
+     If it expands to an empty string, the condition is considered to
+     be false.
+
+     If the condition is true then the second argument, THEN-PART, is
+     evaluated and this is used as the result of the evaluation of the
+     entire `if' function.
+
+     If the condition is false then the third argument, ELSE-PART, is
+     evaluated and this is the result of the `if' function.  If there is
+     no third argument, the `if' function evaluates to nothing (the
+     empty string).
+
+     Note that only one of the THEN-PART or the ELSE-PART will be
+     evaluated, never both.  Thus, either can contain side-effects
+     (such as `shell' function calls, etc.)
+
+`$(or CONDITION1[,CONDITION2[,CONDITION3...]])'
+     The `or' function provides a "short-circuiting" OR operation.
+     Each argument is expanded, in order.  If an argument expands to a
+     non-empty string the processing stops and the result of the
+     expansion is that string.  If, after all arguments are expanded,
+     all of them are false (empty), then the result of the expansion is
+     the empty string.
+
+`$(and CONDITION1[,CONDITION2[,CONDITION3...]])'
+     The `and' function provides a "short-circuiting" AND operation.
+     Each argument is expanded, in order.  If an argument expands to an
+     empty string the processing stops and the result of the expansion
+     is the empty string.  If all arguments expand to a non-empty
+     string then the result of the expansion is the expansion of the
+     last argument.
+
+
+
+File: make.info,  Node: Foreach Function,  Next: Call Function,  Prev: Conditional Functions,  Up: Functions
+
+8.5 The `foreach' Function
+==========================
 
 The `foreach' function is very different from other functions.  It
@@ -5045 +5659 @@
 
 
-File: make.info,  Node: If Function,  Next: Call Function,  Prev: Foreach Function,  Up: Functions
-
-The `if' Function
-=================
-
-The `if' function provides support for conditional expansion in a
-functional context (as opposed to the GNU `make' makefile conditionals
-such as `ifeq' (*note Syntax of Conditionals: Conditional Syntax.).
-
-   An `if' function call can contain either two or three arguments:
-
-     $(if CONDITION,THEN-PART[,ELSE-PART])
-
-   The first argument, CONDITION, first has all preceding and trailing
-whitespace stripped, then is expanded.  If it expands to any non-empty
-string, then the condition is considered to be true.  If it expands to
-an empty string, the condition is considered to be false.
-
-   If the condition is true then the second argument, THEN-PART, is
-evaluated and this is used as the result of the evaluation of the entire
-`if' function.
-
-   If the condition is false then the third argument, ELSE-PART, is
-evaluated and this is the result of the `if' function.  If there is no
-third argument, the `if' function evaluates to nothing (the empty
-string).
-
-   Note that only one of the THEN-PART or the ELSE-PART will be
-evaluated, never both.  Thus, either can contain side-effects (such as
-`shell' function calls, etc.)
-
-
-File: make.info,  Node: Call Function,  Next: Value Function,  Prev: If Function,  Up: Functions
-
-The `call' Function
-===================
+File: make.info,  Node: Call Function,  Next: Value Function,  Prev: Foreach Function,  Up: Functions
+
+8.6 The `call' Function
+=======================
 
 The `call' function is unique in that it can be used to create new
@@ -5119 +5701 @@
 
      reverse = $(2) $(1)
-     
+
      foo = $(call reverse,a,b)
 
@@ -5128 +5710 @@
 
      pathsearch = $(firstword $(wildcard $(addsuffix /$(1),$(subst :, ,$(PATH)))))
-     
+
      LS := $(call pathsearch,ls)
 
@@ -5156 +5738 @@
 File: make.info,  Node: Value Function,  Next: Eval Function,  Prev: Call Function,  Up: Functions
 
-The `value' Function
-====================
+8.7 The `value' Function
+========================
 
 The `value' function provides a way for you to use the value of a
@@ -5180 +5762 @@
 
      FOO = $PATH
-     
+
      all:
              @echo $(FOO)
@@ -5196 +5778 @@
 File: make.info,  Node: Eval Function,  Next: Origin Function,  Prev: Value Function,  Up: Functions
 
-The `eval' Function
-===================
+8.8 The `eval' Function
+=======================
 
 The `eval' function is very special: it allows you to define new
@@ -5228 +5810 @@
 
      PROGRAMS    = server client
-     
+
      server_OBJS = server.o server_priv.o server_access.o
      server_LIBS = priv protocol
-     
+
      client_OBJS = client.o client_api.o client_mem.o
      client_LIBS = protocol
-     
+
      # Everything after this is generic
-     
+
      .PHONY: all
      all: $(PROGRAMS)
-     
+
      define PROGRAM_template
       $(1): $$($(1)_OBJS) $$($(1)_LIBS:%=-l%)
       ALL_OBJS   += $$($(1)_OBJS)
      endef
-     
+
      $(foreach prog,$(PROGRAMS),$(eval $(call PROGRAM_template,$(prog))))
-     
+
      $(PROGRAMS):
              $(LINK.o) $^ $(LDLIBS) -o $@
-     
+
      clean:
              rm -f $(ALL_OBJS) $(PROGRAMS)
 
 
-File: make.info,  Node: Origin Function,  Next: Shell Function,  Prev: Eval Function,  Up: Functions
-
-The `origin' Function
-=====================
+File: make.info,  Node: Origin Function,  Next: Flavor Function,  Prev: Eval Function,  Up: Functions
+
+8.9 The `origin' Function
+=========================
 
 The `origin' function is unlike most other functions in that it does
@@ -5340 +5922 @@
 
 
-File: make.info,  Node: Shell Function,  Next: Make Control Functions,  Prev: Origin Function,  Up: Functions
-
-The `shell' Function
-====================
+File: make.info,  Node: Flavor Function,  Next: Shell Function,  Prev: Origin Function,  Up: Functions
+
+8.10 The `flavor' Function
+==========================
+
+The `flavor' function is unlike most other functions (and like `origin'
+function) in that it does not operate on the values of variables; it
+tells you something _about_ a variable.  Specifically, it tells you the
+flavor of a variable (*note The Two Flavors of Variables: Flavors.).
+
+   The syntax of the `flavor' function is:
+
+     $(flavor VARIABLE)
+
+   Note that VARIABLE is the _name_ of a variable to inquire about; not
+a _reference_ to that variable.  Therefore you would not normally use a
+`$' or parentheses when writing it.  (You can, however, use a variable
+reference in the name if you want the name not to be a constant.)
+
+   The result of this function is a string that identifies the flavor
+of the variable VARIABLE:
+
+`undefined'
+     if VARIABLE was never defined.
+
+`recursive'
+     if VARIABLE is a recursively expanded variable.
+
+`simple'
+     if VARIABLE is a simply expanded variable.
+
+
+
+File: make.info,  Node: Shell Function,  Next: Make Control Functions,  Prev: Flavor Function,  Up: Functions
+
+8.11 The `shell' Function
+=========================
 
 The `shell' function is unlike any other function other than the
@@ -5374 +5989 @@
 
 sets `files' to the expansion of `*.c'.  Unless `make' is using a very
-strange shell, this has the same result as `$(wildcard *.c)'.
+strange shell, this has the same result as `$(wildcard *.c)' (as long
+as at least one `.c' file exists).
 
 
 File: make.info,  Node: Make Control Functions,  Prev: Shell Function,  Up: Functions
 
-Functions That Control Make
-===========================
+8.12 Functions That Control Make
+================================
 
 These functions control the way make runs.  Generally, they are used to
@@ -5403 +6019 @@
 
           ERR = $(error found an error!)
-          
+
           .PHONY: err
           err: ; $(ERR)
@@ -5418 +6034 @@
      The result of the expansion of this function is the empty string.
 
+`$(info TEXT...)'
+     This function does nothing more than print its (expanded)
+     argument(s) to standard output.  No makefile name or line number
+     is added.  The result of the expansion of this function is the
+     empty string.
+
 
 File: make.info,  Node: Running,  Next: Implicit Rules,  Prev: Functions,  Up: Top
 
-How to Run `make'
-*****************
+9 How to Run `make'
+*******************
 
 A makefile that says how to recompile a program can be used in more
@@ -5468 +6090 @@
 File: make.info,  Node: Makefile Arguments,  Next: Goals,  Prev: Running,  Up: Running
 
-Arguments to Specify the Makefile
-=================================
+9.1 Arguments to Specify the Makefile
+=====================================
 
 The way to specify the name of the makefile is with the `-f' or
@@ -5486 +6108 @@
 File: make.info,  Node: Goals,  Next: Instead of Execution,  Prev: Makefile Arguments,  Up: Running
 
-Arguments to Specify the Goals
-==============================
+9.2 Arguments to Specify the Goals
+==================================
 
 The "goals" are the targets that `make' should strive ultimately to
@@ -5498 +6120 @@
 program or programs they describe.  If the first rule in the makefile
 has several targets, only the first target in the rule becomes the
-default goal, not the whole list.
-
-   You can specify a different goal or goals with arguments to `make'.
-Use the name of the goal as an argument.  If you specify several goals,
-`make' processes each of them in turn, in the order you name them.
+default goal, not the whole list.  You can manage the selection of the
+default goal from within your makefile using the `.DEFAULT_GOAL'
+variable (*note Other Special Variables: Special Variables.).
+
+   You can also specify a different goal or goals with command-line
+arguments to `make'.  Use the name of the goal as an argument.  If you
+specify several goals, `make' processes each of them in turn, in the
+order you name them.
 
    Any target in the makefile may be specified as a goal (unless it
@@ -5520 +6145 @@
 
      sources = foo.c bar.c
-     
+
      ifneq ($(MAKECMDGOALS),clean)
      include $(sources:.c=.d)
@@ -5600 +6225 @@
 File: make.info,  Node: Instead of Execution,  Next: Avoiding Compilation,  Prev: Goals,  Up: Running
 
-Instead of Executing the Commands
-=================================
+9.3 Instead of Executing the Commands
+=====================================
 
 The makefile tells `make' how to tell whether a target is up to date,
@@ -5679 +6304 @@
 File: make.info,  Node: Avoiding Compilation,  Next: Overriding,  Prev: Instead of Execution,  Up: Running
 
-Avoiding Recompilation of Some Files
-====================================
+9.4 Avoiding Recompilation of Some Files
+========================================
 
 Sometimes you may have changed a source file but you do not want to
@@ -5722 +6347 @@
 File: make.info,  Node: Overriding,  Next: Testing,  Prev: Avoiding Compilation,  Up: Running
 
-Overriding Variables
-====================
+9.5 Overriding Variables
+========================
 
 An argument that contains `=' specifies the value of a variable: `V=X'
@@ -5774 +6399 @@
 File: make.info,  Node: Testing,  Next: Options Summary,  Prev: Overriding,  Up: Running
 
-Testing the Compilation of a Program
-====================================
+9.6 Testing the Compilation of a Program
+========================================
 
 Normally, when an error happens in executing a shell command, `make'
@@ -5810 +6435 @@
 File: make.info,  Node: Options Summary,  Prev: Testing,  Up: Running
 
-Summary of Options
-==================
+9.7 Summary of Options
+======================
 
 Here is a table of all the options `make' understands:
@@ -5824 +6449 @@
      Consider all targets out-of-date.  GNU `make' proceeds to consider
      targets and their prerequisites using the normal algorithms;
-     however, all these targets are remade, regardless of the status of
-     their prerequisites.
+     however, all targets so considered are always remade regardless of
+     the status of their prerequisites.  To avoid infinite recursion, if
+     `MAKE_RESTARTS' (*note Other Special Variables: Special
+     Variables.) is set to a number greater than 0 this option is
+     disabled when considering whether to remake makefiles (*note How
+     Makefiles Are Remade: Remaking Makefiles.).
 
 `-C DIR'
@@ -5930 +6559 @@
      floating-point number).  With no argument, removes a previous load
      limit.  *Note Parallel Execution: Parallel.
+
+`-L'
+`--check-symlink-times'
+     On systems that support symbolic links, this option causes `make'
+     to consider the timestamps on any symbolic links in addition to the
+     timestamp on the file referenced by those links.  When this option
+     is provided, the most recent timestamp among the file and the
+     symbolic links is taken as the modification time for this target
+     file.
 
 `-n'
@@ -6052 +6690 @@
 File: make.info,  Node: Implicit Rules,  Next: Archives,  Prev: Running,  Up: Top
 
-Using Implicit Rules
-********************
+10 Using Implicit Rules
+***********************
 
 Certain standard ways of remaking target files are used very often.  For
@@ -6090 +6728 @@
 * Chained Rules::               How to use a chain of implicit rules.
 * Pattern Rules::               How to define new implicit rules.
-* Last Resort::                 How to defining commands for rules
-                                  which cannot find any.
+* Last Resort::                 How to define commands for rules which
+                                  cannot find any.
 * Suffix Rules::                The old-fashioned style of implicit rule.
 * Implicit Rule Search::        The precise algorithm for applying
@@ -6099 +6737 @@
 File: make.info,  Node: Using Implicit,  Next: Catalogue of Rules,  Prev: Implicit Rules,  Up: Implicit Rules
 
-Using Implicit Rules
-====================
+10.1 Using Implicit Rules
+=========================
 
 To allow `make' to find a customary method for updating a target file,
@@ -6173 +6811 @@
 File: make.info,  Node: Catalogue of Rules,  Next: Implicit Variables,  Prev: Using Implicit,  Up: Implicit Rules
 
-Catalogue of Implicit Rules
-===========================
+10.2 Catalogue of Implicit Rules
+================================
 
 Here is a catalogue of predefined implicit rules which are always
@@ -6182 +6820 @@
 `--no-builtin-rules' option cancels all predefined rules.
 
+   This manual only documents the default rules available on POSIX-based
+operating systems.  Other operating systems, such as VMS, Windows,
+OS/2, etc. may have different sets of default rules.  To see the full
+list of default rules and variables available in your version of GNU
+`make', run `make -p' in a directory with no makefile.
+
    Not all of these rules will always be defined, even when the `-r'
 option is not given.  Many of the predefined implicit rules are
@@ -6187 +6831 @@
 depends on the "suffix list" (the list of prerequisites of the special
 target `.SUFFIXES').  The default suffix list is: `.out', `.a', `.ln',
-`.o', `.c', `.cc', `.C', `.p', `.f', `.F', `.r', `.y', `.l', `.s',
-`.S', `.mod', `.sym', `.def', `.h', `.info', `.dvi', `.tex', `.texinfo',
-`.texi', `.txinfo', `.w', `.ch' `.web', `.sh', `.elc', `.el'.  All of
-the implicit rules described below whose prerequisites have one of
-these suffixes are actually suffix rules.  If you modify the suffix
-list, the only predefined suffix rules in effect will be those named by
-one or two of the suffixes that are on the list you specify; rules
-whose suffixes fail to be on the list are disabled.  *Note
-Old-Fashioned Suffix Rules: Suffix Rules, for full details on suffix
-rules.
+`.o', `.c', `.cc', `.C', `.cpp', `.p', `.f', `.F', `.r', `.y', `.l',
+`.s', `.S', `.mod', `.sym', `.def', `.h', `.info', `.dvi', `.tex',
+`.texinfo', `.texi', `.txinfo', `.w', `.ch' `.web', `.sh', `.elc',
+`.el'.  All of the implicit rules described below whose prerequisites
+have one of these suffixes are actually suffix rules.  If you modify
+the suffix list, the only predefined suffix rules in effect will be
+those named by one or two of the suffixes that are on the list you
+specify; rules whose suffixes fail to be on the list are disabled.
+*Note Old-Fashioned Suffix Rules: Suffix Rules, for full details on
+suffix rules.
 
 Compiling C programs
@@ -6203 +6847 @@
 
 Compiling C++ programs
-     `N.o' is made automatically from `N.cc' or `N.C' with a command of
-     the form `$(CXX) -c $(CPPFLAGS) $(CXXFLAGS)'.  We encourage you to
-     use the suffix `.cc' for C++ source files instead of `.C'.
+     `N.o' is made automatically from `N.cc', `N.cpp', or `N.C' with a
+     command of the form `$(CXX) -c $(CPPFLAGS) $(CXXFLAGS)'.  We
+     encourage you to use the suffix `.cc' for C++ source files instead
+     of `.C'.
 
 Compiling Pascal programs
@@ -6379 +7024 @@
 File: make.info,  Node: Implicit Variables,  Next: Chained Rules,  Prev: Catalogue of Rules,  Up: Implicit Rules
 
-Variables Used by Implicit Rules
-================================
+10.3 Variables Used by Implicit Rules
+=====================================
 
 The commands in built-in implicit rules make liberal use of certain
-predefined variables.  You can alter these variables in the makefile,
-with arguments to `make', or in the environment to alter how the
-implicit rules work without redefining the rules themselves.  You can
-cancel all variables used by implicit rules with the `-R' or
+predefined variables.  You can alter the values of these variables in
+the makefile, with arguments to `make', or in the environment to alter
+how the implicit rules work without redefining the rules themselves.
+You can cancel all variables used by implicit rules with the `-R' or
 `--no-builtin-variables' option.
 
@@ -6406 +7051 @@
 argument, separate them with spaces.
 
-   Here is a table of variables used as names of programs in built-in
-rules:
+   The following tables describe of some of the more commonly-used
+predefined variables.  This list is not exhaustive, and the default
+values shown here may not be what are selected by `make' for your
+environment.  To see the complete list of predefined variables for your
+instance of GNU `make' you can run `make -p' in a directory with no
+makefiles.
+
+   Here is a table of some of the more common variables used as names of
+programs in built-in rules: makefiles.
 
 `AR'
-     Archive-maintaining program; default `ar'.
+     Archive-maintaining program; default `ar'.  
 
 `AS'
-     Program for doing assembly; default `as'.
+     Program for compiling assembly files; default `as'.  
 
 `CC'
-     Program for compiling C programs; default `cc'.
+     Program for compiling C programs; default `cc'.  
+
+`CO'
+     Program for checking out files from RCS; default `co'.  
 
 `CXX'
-     Program for compiling C++ programs; default `g++'.
+     Program for compiling C++ programs; default `g++'.  
 
 `CO'
-     Program for extracting a file from RCS; default `co'.
+     Program for extracting a file from RCS; default `co'.  
 
 `CPP'
@@ -6430 +7085 @@
 `FC'
      Program for compiling or preprocessing Fortran and Ratfor programs;
-     default `f77'.
+     default `f77'.  
 
 `GET'
-     Program for extracting a file from SCCS; default `get'.
+     Program for extracting a file from SCCS; default `get'.  
 
 `LEX'
-     Program to use to turn Lex grammars into C programs or Ratfor
-     programs; default `lex'.
+     Program to use to turn Lex grammars into source code; default
+     `lex'.  
+
+`YACC'
+     Program to use to turn Yacc grammars into source code; default
+     `yacc'.  
+
+`LINT'
+     Program to use to run lint on source code; default `lint'.  
+
+`M2C'
+     Program to use to compile Modula-2 source code; default `m2c'.  
 
 `PC'
-     Program for compiling Pascal programs; default `pc'.
-
-`YACC'
-     Program to use to turn Yacc grammars into C programs; default
-     `yacc'.
-
-`YACCR'
-     Program to use to turn Yacc grammars into Ratfor programs; default
-     `yacc -r'.
+     Program for compiling Pascal programs; default `pc'.  
 
 `MAKEINFO'
      Program to convert a Texinfo source file into an Info file; default
-     `makeinfo'.
+     `makeinfo'.  
 
 `TEX'
-     Program to make TeX DVI files from TeX source; default `tex'.
+     Program to make TeX DVI files from TeX source; default `tex'.  
 
 `TEXI2DVI'
      Program to make TeX DVI files from Texinfo source; default
-     `texi2dvi'.
+     `texi2dvi'.  
 
 `WEAVE'
-     Program to translate Web into TeX; default `weave'.
+     Program to translate Web into TeX; default `weave'.  
 
 `CWEAVE'
-     Program to translate C Web into TeX; default `cweave'.
+     Program to translate C Web into TeX; default `cweave'.  
 
 `TANGLE'
-     Program to translate Web into Pascal; default `tangle'.
+     Program to translate Web into Pascal; default `tangle'.  
 
 `CTANGLE'
-     Program to translate C Web into C; default `ctangle'.
+     Program to translate C Web into C; default `ctangle'.  
 
 `RM'
-     Command to remove a file; default `rm -f'.
+     Command to remove a file; default `rm -f'.  
 
    Here is a table of variables whose values are additional arguments
@@ -6513 +7170 @@
      Extra flags to give to Lex.
 
+`YFLAGS'
+     Extra flags to give to Yacc.
+
 `PFLAGS'
      Extra flags to give to the Pascal compiler.
@@ -6519 +7179 @@
      Extra flags to give to the Fortran compiler for Ratfor programs.
 
-`YFLAGS'
-     Extra flags to give to Yacc.
+`LINTFLAGS'
+     Extra flags to give to lint.
 
 
 File: make.info,  Node: Chained Rules,  Next: Pattern Rules,  Prev: Implicit Variables,  Up: Implicit Rules
 
-Chains of Implicit Rules
-========================
+10.4 Chains of Implicit Rules
+=============================
 
 Sometimes a file can be made by a sequence of implicit rules.  For
@@ -6578 +7238 @@
 as a prerequisite of the special target `.PRECIOUS' to preserve
 intermediate files made by implicit rules whose target patterns match
-that file's name; see *Note Interrupts::.
+that file's name; see *Note Interrupts::.  
 
    A chain can involve more than two implicit rules.  For example, it is
@@ -6600 +7260 @@
 earlier in the ordering of rules.
 
-
-File: make.info,  Node: Pattern Rules,  Next: Last Resort,  Prev: Chained Rules,  Up: Implicit Rules
-
-Defining and Redefining Pattern Rules
-=====================================
-
-You define an implicit rule by writing a "pattern rule".  A pattern
-rule looks like an ordinary rule, except that its target contains the
-character `%' (exactly one of them).  The target is considered a
-pattern for matching file names; the `%' can match any nonempty
-substring, while other characters match only themselves.  The
-prerequisites likewise use `%' to show how their names relate to the
-target name.
-
-   Thus, a pattern rule `%.o : %.c' says how to make any file `STEM.o'
-from another file `STEM.c'.
-
-   Note that expansion using `%' in pattern rules occurs *after* any
-variable or function expansions, which take place when the makefile is
-read.  *Note How to Use Variables: Using Variables, and *Note Functions
-for Transforming Text: Functions.
-
-* Menu:
-
-* Pattern Intro::               An introduction to pattern rules.
-* Pattern Examples::            Examples of pattern rules.
-* Automatic Variables::         How to use automatic variables in the
-                                  commands of implicit rules.
-* Pattern Match::               How patterns match.
-* Match-Anything Rules::        Precautions you should take prior to
-                                  defining rules that can match any
-                                  target file whatever.
-* Canceling Rules::             How to override or cancel built-in rules.
-
-
-File: make.info,  Node: Pattern Intro,  Next: Pattern Examples,  Prev: Pattern Rules,  Up: Pattern Rules
-
-Introduction to Pattern Rules
------------------------------
-
-A pattern rule contains the character `%' (exactly one of them) in the
-target; otherwise, it looks exactly like an ordinary rule.  The target
-is a pattern for matching file names; the `%' matches any nonempty
-substring, while other characters match only themselves.
-
-   For example, `%.c' as a pattern matches any file name that ends in
-`.c'.  `s.%.c' as a pattern matches any file name that starts with
-`s.', ends in `.c' and is at least five characters long.  (There must
-be at least one character to match the `%'.)  The substring that the
-`%' matches is called the "stem".
-
-   `%' in a prerequisite of a pattern rule stands for the same stem
-that was matched by the `%' in the target.  In order for the pattern
-rule to apply, its target pattern must match the file name under
-consideration, and its prerequisite patterns must name files that exist
-or can be made.  These files become prerequisites of the target.
-
-   Thus, a rule of the form
-
-     %.o : %.c ; COMMAND...
-
-specifies how to make a file `N.o', with another file `N.c' as its
-prerequisite, provided that `N.c' exists or can be made.
-
-   There may also be prerequisites that do not use `%'; such a
-prerequisite attaches to every file made by this pattern rule.  These
-unvarying prerequisites are useful occasionally.
-
-   A pattern rule need not have any prerequisites that contain `%', or
-in fact any prerequisites at all.  Such a rule is effectively a general
-wildcard.  It provides a way to make any file that matches the target
-pattern.  *Note Last Resort::.
-
-   Pattern rules may have more than one target.  Unlike normal rules,
-this does not act as many different rules with the same prerequisites
-and commands.  If a pattern rule has multiple targets, `make' knows that
-the rule's commands are responsible for making all of the targets.  The
-commands are executed only once to make all the targets.  When searching
-for a pattern rule to match a target, the target patterns of a rule
-other than the one that matches the target in need of a rule are
-incidental: `make' worries only about giving commands and prerequisites
-to the file presently in question.  However, when this file's commands
-are run, the other targets are marked as having been updated themselves.
-
-   The order in which pattern rules appear in the makefile is important
-since this is the order in which they are considered.  Of equally
-applicable rules, only the first one found is used.  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.
-
-
-File: make.info,  Node: Pattern Examples,  Next: Automatic Variables,  Prev: Pattern Intro,  Up: Pattern Rules
-
-Pattern Rule Examples
----------------------
-
-Here are some examples of pattern rules actually predefined in `make'.
-First, the rule that compiles `.c' files into `.o' files:
-
-     %.o : %.c
-             $(CC) -c $(CFLAGS) $(CPPFLAGS) $< -o $@
-
-defines a rule that can make any file `X.o' from `X.c'.  The command
-uses the automatic variables `$@' and `$<' to substitute the names of
-the target file and the source file in each case where the rule applies
-(*note Automatic Variables::).
-
-   Here is a second built-in rule:
-
-     % :: RCS/%,v
-             $(CO) $(COFLAGS) $<
-
-defines a rule that can make any file `X' whatsoever from a
-corresponding file `X,v' in the subdirectory `RCS'.  Since the target
-is `%', this rule will apply to any file whatever, provided the
-appropriate prerequisite file exists.  The double colon makes the rule
-"terminal", which means that its prerequisite may not be an intermediate
-file (*note Match-Anything Pattern Rules: Match-Anything Rules.).
-
-   This pattern rule has two targets:
-
-     %.tab.c %.tab.h: %.y
-             bison -d $<
-
-This tells `make' that the command `bison -d X.y' will make both
-`X.tab.c' and `X.tab.h'.  If the file `foo' depends on the files
-`parse.tab.o' and `scan.o' and the file `scan.o' depends on the file
-`parse.tab.h', when `parse.y' is changed, the command `bison -d parse.y'
-will be executed only once, and the prerequisites of both `parse.tab.o'
-and `scan.o' will be satisfied.  (Presumably the file `parse.tab.o'
-will be recompiled from `parse.tab.c' and the file `scan.o' from
-`scan.c', while `foo' is linked from `parse.tab.o', `scan.o', and its
-other prerequisites, and it will execute happily ever after.)
-
-
-File: make.info,  Node: Automatic Variables,  Next: Pattern Match,  Prev: Pattern Examples,  Up: Pattern Rules
-
-Automatic Variables
--------------------
-
-Suppose you are writing a pattern rule to compile a `.c' file into a
-`.o' file: how do you write the `cc' command so that it operates on the
-right source file name?  You cannot write the name in the command,
-because the name is different each time the implicit rule is applied.
-
-   What you do is use a special feature of `make', the "automatic
-variables".  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 `$@' for the object file name and `$<'
-for the source file name.
-
-   It's very important that you recognize the limited scope in which
-automatic variable values are available: they only have values within
-the command script.  In particular, you cannot use them anywhere within
-the target or prerequisite lists of a rule; they have no value there
-and will expand to the empty string.  A common mistake is attempting to
-use `$@' within the prerequisites list in a rule; this will not work.
-However, see below for information on the SysV-style `$$@' variables.
-
-   Here is a table of automatic variables:
-
-`$@'
-     The file name of the target of the rule.  If the target is an
-     archive member, then `$@' is the name of the archive file.  In a
-     pattern rule that has multiple targets (*note Introduction to
-     Pattern Rules: Pattern Intro.), `$@' is the name of whichever
-     target caused the rule's commands to be run.
-
-`$%'
-     The target member name, when the target is an archive member.
-     *Note Archives::.  For example, if the target is `foo.a(bar.o)'
-     then `$%' is `bar.o' and `$@' is `foo.a'.  `$%' is empty when the
-     target is not an archive member.
-
-`$<'
-     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 implicit rule (*note Implicit Rules::).
-
-`$?'
-     The names of all the prerequisites that are newer than the target,
-     with spaces between them.  For prerequisites which are archive
-     members, only the member named is used (*note Archives::).
-
-`$^'
-     The names of all the prerequisites, with spaces between them.  For
-     prerequisites which are archive members, only the member named is
-     used (*note Archives::).  A target has only one prerequisite on
-     each other file it depends on, no matter how many times each file
-     is listed as a prerequisite.  So if you list a prerequisite more
-     than once for a target, the value of `$^' contains just one copy
-     of the name.
-
-`$+'
-     This is like `$^', but prerequisites listed more than once are
-     duplicated in the order they were listed in the makefile.  This is
-     primarily useful for use in linking commands where it is
-     meaningful to repeat library file names in a particular order.
-
-`$*'
-     The stem with which an implicit rule matches (*note How Patterns
-     Match: Pattern Match.).  If the target is `dir/a.foo.b' and the
-     target pattern is `a.%.b' then the stem is `dir/foo'.  The stem is
-     useful for constructing names of related files.
-
-     In a static pattern rule, the stem is part of the file name that
-     matched the `%' in the target pattern.
-
-     In an explicit rule, there is no stem; so `$*' cannot be determined
-     in that way.  Instead, if the target name ends with a recognized
-     suffix (*note Old-Fashioned Suffix Rules: Suffix Rules.), `$*' is
-     set to the target name minus the suffix.  For example, if the
-     target name is `foo.c', then `$*' is set to `foo', since `.c' is a
-     suffix.  GNU `make' does this bizarre thing only for compatibility
-     with other implementations of `make'.  You should generally avoid
-     using `$*' except in implicit rules or static pattern rules.
-
-     If the target name in an explicit rule does not end with a
-     recognized suffix, `$*' is set to the empty string for that rule.
-
-   `$?' is useful even in explicit rules when you wish to operate on
-only the prerequisites that have changed.  For example, suppose that an
-archive named `lib' is supposed to contain copies of several object
-files.  This rule copies just the changed object files into the archive:
-
-     lib: foo.o bar.o lose.o win.o
-             ar r lib $?
-
-   Of the variables listed above, four have values that are single file
-names, and three have values that are lists of file names.  These seven
-have variants that get just the file's directory name or just the file
-name within the directory.  The variant variables' names are formed by
-appending `D' or `F', respectively.  These variants are semi-obsolete
-in GNU `make' since the functions `dir' and `notdir' can be used to get
-a similar effect (*note Functions for File Names: File Name
-Functions.).  Note, however, that the `D' variants all omit the
-trailing slash which always appears in the output of the `dir'
-function.  Here is a table of the variants:
-
-`$(@D)'
-     The directory part of the file name of the target, with the
-     trailing slash removed.  If the value of `$@' is `dir/foo.o' then
-     `$(@D)' is `dir'.  This value is `.' if `$@' does not contain a
-     slash.
-
-`$(@F)'
-     The file-within-directory part of the file name of the target.  If
-     the value of `$@' is `dir/foo.o' then `$(@F)' is `foo.o'.  `$(@F)'
-     is equivalent to `$(notdir $@)'.
-
-`$(*D)'
-`$(*F)'
-     The directory part and the file-within-directory part of the stem;
-     `dir' and `foo' in this example.
-
-`$(%D)'
-`$(%F)'
-     The directory part and the file-within-directory part of the target
-     archive member name.  This makes sense only for archive member
-     targets of the form `ARCHIVE(MEMBER)' and is useful only when
-     MEMBER may contain a directory name.  (*Note Archive Members as
-     Targets: Archive Members.)
-
-`$(<D)'
-`$(<F)'
-     The directory part and the file-within-directory part of the first
-     prerequisite.
-
-`$(^D)'
-`$(^F)'
-     Lists of the directory parts and the file-within-directory parts
-     of all prerequisites.
-
-`$(+D)'
-`$(+F)'
-     Lists of the directory parts and the file-within-directory parts
-     of all prerequisites, including multiple instances of duplicated
-     prerequisites.
-
-`$(?D)'
-`$(?F)'
-     Lists of the directory parts and the file-within-directory parts of
-     all prerequisites that are newer than the target.
-
-   Note that we use a special stylistic convention when we talk about
-these automatic variables; we write "the value of `$<'", rather than
-"the variable `<'" as we would write for ordinary variables such as
-`objects' and `CFLAGS'.  We think this convention looks more natural in
-this special case.  Please do not assume it has a deep significance;
-`$<' refers to the variable named `<' just as `$(CFLAGS)' refers to the
-variable named `CFLAGS'.  You could just as well use `$(<)' in place of
-`$<'.
-
-   GNU `make' provides support for the SysV `make' feature that allows
-special variable references `$$@', `$$(@D)', and `$$(@F)' (note the
-required double-"$"!) to appear with the _prerequisites list_ (normal
-automatic variables are available only within a command script).  When
-appearing in a prerequisites list, these variables are expanded to the
-name of the target, the directory component of the target, and the file
-component of the target, respectively.
-
-   Note that these variables are available only within explicit and
-static pattern (*note Static Pattern Rules: Static Pattern.) rules;
-they have no special significance within implicit (suffix or pattern)
-rules.  Also note that while SysV `make' actually expands its entire
-prerequisite list _twice_, GNU `make' does not behave this way: instead
-it simply expands these special variables without re-expanding any
-other part of the prerequisites list.
-
-   This somewhat bizarre feature is included only to provide some
-compatibility with SysV makefiles.  In a native GNU `make' file there
-are other ways to accomplish the same results.  This feature is
-disabled if the special pseudo target `.POSIX' is defined.
-
-
-File: make.info,  Node: Pattern Match,  Next: Match-Anything Rules,  Prev: Automatic Variables,  Up: Pattern Rules
-
-How Patterns Match
-------------------
-
-A target pattern is composed of a `%' between a prefix and a suffix,
-either or both of which may be empty.  The pattern matches a file name
-only if the file name starts with the prefix and ends with the suffix,
-without overlap.  The text between the prefix and the suffix is called
-the "stem".  Thus, when the pattern `%.o' matches the file name
-`test.o', the stem is `test'.  The pattern rule prerequisites are
-turned into actual file names by substituting the stem for the character
-`%'.  Thus, if in the same example one of the prerequisites is written
-as `%.c', it expands to `test.c'.
-
-   When the target pattern does not contain a slash (and it usually does
-not), directory names in the file names are removed from the file name
-before it is compared with the target prefix and suffix.  After the
-comparison of the file name to the target pattern, the directory names,
-along with the slash that ends them, are added on to the prerequisite
-file names generated from the pattern rule's prerequisite patterns and
-the file name. The directories are ignored only for the purpose of
-finding an implicit rule to use, not in the application of that rule.
-Thus, `e%t' matches the file name `src/eat', with `src/a' as the stem.
-When prerequisites are turned into file names, the directories from the
-stem are added at the front, while the rest of the stem is substituted
-for the `%'.  The stem `src/a' with a prerequisite pattern `c%r' gives
-the file name `src/car'.
-
-
-File: make.info,  Node: Match-Anything Rules,  Next: Canceling Rules,  Prev: Pattern Match,  Up: Pattern Rules
-
-Match-Anything Pattern Rules
-----------------------------
-
-When a pattern rule's target is just `%', it matches any file name
-whatever.  We call these rules "match-anything" rules.  They are very
-useful, but it can take a lot of time for `make' to think about them,
-because it must consider every such rule for each file name listed
-either as a target or as a prerequisite.
-
-   Suppose the makefile mentions `foo.c'.  For this target, `make'
-would have to consider making it by linking an object file `foo.c.o',
-or by C compilation-and-linking in one step from `foo.c.c', or by
-Pascal compilation-and-linking from `foo.c.p', and many other
-possibilities.
-
-   We know these possibilities are ridiculous since `foo.c' is a C
-source file, not an executable.  If `make' did consider these
-possibilities, it would ultimately reject them, because files such as
-`foo.c.o' and `foo.c.p' would not exist.  But these possibilities are so
-numerous that `make' would run very slowly if it had to consider them.
-
-   To gain speed, we have put various constraints on the way `make'
-considers match-anything rules.  There are two different constraints
-that can be applied, and each time you define a match-anything rule you
-must choose one or the other for that rule.
-
-   One choice is to mark the match-anything rule as "terminal" by
-defining it with a double colon.  When a rule is terminal, it does not
-apply unless its prerequisites actually exist.  Prerequisites that
-could be made with other implicit rules are not good enough.  In other
-words, no further chaining is allowed beyond a terminal rule.
-
-   For example, the built-in implicit rules for extracting sources from
-RCS and SCCS files are terminal; as a result, if the file `foo.c,v' does
-not exist, `make' will not even consider trying to make it as an
-intermediate file from `foo.c,v.o' or from `RCS/SCCS/s.foo.c,v'.  RCS
-and SCCS files are generally ultimate source files, which should not be
-remade from any other files; therefore, `make' can save time by not
-looking for ways to remake them.
-
-   If you do not mark the match-anything rule as terminal, then it is
-nonterminal.  A nonterminal match-anything rule cannot apply to a file
-name that indicates a specific type of data.  A file name indicates a
-specific type of data if some non-match-anything implicit rule target
-matches it.
-
-   For example, the file name `foo.c' matches the target for the pattern
-rule `%.c : %.y' (the rule to run Yacc).  Regardless of whether this
-rule is actually applicable (which happens only if there is a file
-`foo.y'), the fact that its target matches is enough to prevent
-consideration of any nonterminal match-anything rules for the file
-`foo.c'.  Thus, `make' will not even consider trying to make `foo.c' as
-an executable file from `foo.c.o', `foo.c.c', `foo.c.p', etc.
-
-   The motivation for this constraint is that nonterminal match-anything
-rules are used for making files containing specific types of data (such
-as executable files) and a file name with a recognized suffix indicates
-some other specific type of data (such as a C source file).
-
-   Special built-in dummy pattern rules are provided solely to recognize
-certain file names so that nonterminal match-anything rules will not be
-considered.  These dummy rules have no prerequisites and no commands,
-and they are ignored for all other purposes.  For example, the built-in
-implicit rule
-
-     %.p :
-
-exists to make sure that Pascal source files such as `foo.p' match a
-specific target pattern and thereby prevent time from being wasted
-looking for `foo.p.o' or `foo.p.c'.
-
-   Dummy pattern rules such as the one for `%.p' are made for every
-suffix listed as valid for use in suffix rules (*note Old-Fashioned
-Suffix Rules: Suffix Rules.).
-
-
-File: make.info,  Node: Canceling Rules,  Prev: Match-Anything Rules,  Up: Pattern Rules
-
-Canceling Implicit Rules
-------------------------
-
-You can override a built-in implicit rule (or one you have defined
-yourself) by defining a new pattern rule with the same target and
-prerequisites, but different commands.  When the new rule is defined,
-the built-in one is replaced.  The new rule's position in the sequence
-of implicit rules is determined by where you write the new rule.
-
-   You can cancel a built-in implicit rule by defining a pattern rule
-with the same target and prerequisites, but no commands.  For example,
-the following would cancel the rule that runs the assembler:
-
-     %.o : %.s
-
-
-File: make.info,  Node: Last Resort,  Next: Suffix Rules,  Prev: Pattern Rules,  Up: Implicit Rules
-
-Defining Last-Resort Default Rules
-==================================
-
-You can define a last-resort implicit rule by writing a terminal
-match-anything pattern rule with no prerequisites (*note Match-Anything
-Rules::).  This is just like any other pattern rule; the only thing
-special about it is that it will match any target.  So such a rule's
-commands are used for all targets and prerequisites that have no
-commands of their own and for which no other implicit rule applies.
-
-   For example, when testing a makefile, you might not care if the
-source files contain real data, only that they exist.  Then you might
-do this:
-
-     %::
-             touch $@
-
-to cause all the source files needed (as prerequisites) to be created
-automatically.
-
-   You can instead define commands to be used for targets for which
-there are no rules at all, even ones which don't specify commands.  You
-do this by writing a rule for the target `.DEFAULT'.  Such a rule's
-commands are used for all prerequisites which do not appear as targets
-in any explicit rule, and for which no implicit rule applies.
-Naturally, there is no `.DEFAULT' rule unless you write one.
-
-   If you use `.DEFAULT' with no commands or prerequisites:
-
-     .DEFAULT:
-
-the commands previously stored for `.DEFAULT' are cleared.  Then `make'
-acts as if you had never defined `.DEFAULT' at all.
-
-   If you do not want a target to get the commands from a match-anything
-pattern rule or `.DEFAULT', but you also do not want any commands to be
-run for the target, you can give it empty commands (*note Defining
-Empty Commands: Empty Commands.).
-
-   You can use a last-resort rule to override part of another makefile.
-*Note Overriding Part of Another Makefile: Overriding Makefiles.
-
-
-File: make.info,  Node: Suffix Rules,  Next: Implicit Rule Search,  Prev: Last Resort,  Up: Implicit Rules
-
-Old-Fashioned Suffix Rules
-==========================
-
-"Suffix rules" are the old-fashioned way of defining implicit rules for
-`make'.  Suffix rules are obsolete because pattern rules are more
-general and clearer.  They are supported in GNU `make' for
-compatibility with old makefiles.  They come in two kinds:
-"double-suffix" and "single-suffix".
-
-   A double-suffix rule is defined by a pair of suffixes: the target
-suffix and the source suffix.  It matches any file whose name ends with
-the target suffix.  The corresponding implicit prerequisite is made by
-replacing the target suffix with the source suffix in the file name.  A
-two-suffix rule whose target and source suffixes are `.o' and `.c' is
-equivalent to the pattern rule `%.o : %.c'.
-
-   A single-suffix rule is defined by a single suffix, which is the
-source suffix.  It matches any file name, and the corresponding implicit
-prerequisite name is made by appending the source suffix.  A
-single-suffix rule whose source suffix is `.c' is equivalent to the
-pattern rule `% : %.c'.
-
-   Suffix rule definitions are recognized by comparing each rule's
-target against a defined list of known suffixes.  When `make' sees a
-rule whose target is a known suffix, this rule is considered a
-single-suffix rule.  When `make' sees a rule whose target is two known
-suffixes concatenated, this rule is taken as a double-suffix rule.
-
-   For example, `.c' and `.o' are both on the default list of known
-suffixes.  Therefore, if you define a rule whose target is `.c.o',
-`make' takes it to be a double-suffix rule with source suffix `.c' and
-target suffix `.o'.  Here is the old-fashioned way to define the rule
-for compiling a C source file:
-
-     .c.o:
-             $(CC) -c $(CFLAGS) $(CPPFLAGS) -o $@ $<
-
-   Suffix rules cannot have any prerequisites of their own.  If they
-have any, they are treated as normal files with funny names, not as
-suffix rules.  Thus, the rule:
-
-     .c.o: foo.h
-             $(CC) -c $(CFLAGS) $(CPPFLAGS) -o $@ $<
-
-tells how to make the file `.c.o' from the prerequisite file `foo.h',
-and is not at all like the pattern rule:
-
-     %.o: %.c foo.h
-             $(CC) -c $(CFLAGS) $(CPPFLAGS) -o $@ $<
-
-which tells how to make `.o' files from `.c' files, and makes all `.o'
-files using this pattern rule also depend on `foo.h'.
-
-   Suffix rules with no commands are also meaningless.  They do not
-remove previous rules as do pattern rules with no commands (*note
-Canceling Implicit Rules: Canceling Rules.).  They simply enter the
-suffix or pair of suffixes concatenated as a target in the data base.
-
-   The known suffixes are simply the names of the prerequisites of the
-special target `.SUFFIXES'.  You can add your own suffixes by writing a
-rule for `.SUFFIXES' that adds more prerequisites, as in:
-
-     .SUFFIXES: .hack .win
-
-which adds `.hack' and `.win' to the end of the list of suffixes.
-
-   If you wish to eliminate the default known suffixes instead of just
-adding to them, write a rule for `.SUFFIXES' with no prerequisites.  By
-special dispensation, this eliminates all existing prerequisites of
-`.SUFFIXES'.  You can then write another rule to add the suffixes you
-want.  For example,
-
-     .SUFFIXES:            # Delete the default suffixes
-     .SUFFIXES: .c .o .h   # Define our suffix list
-
-   The `-r' or `--no-builtin-rules' flag causes the default list of
-suffixes to be empty.
-
-   The variable `SUFFIXES' is defined to the default list of suffixes
-before `make' reads any makefiles.  You can change the list of suffixes
-with a rule for the special target `.SUFFIXES', but that does not alter
-this variable.
-

vendor/gnumake/current/doc/make.info-2

@@ -1 @@
-This is make.info, produced by makeinfo version 4.6 from make.texi.
+This is make.info, produced by makeinfo version 4.8 from make.texi.
+
+   This file documents the GNU `make' utility, which determines
+automatically which pieces of a large program need to be recompiled,
+and issues the commands to recompile them.
+
+   This is Edition 0.70, last updated 1 April 2006, of `The GNU Make
+Manual', for GNU `make' version 3.81.
+
+   Copyright (C) 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996,
+1997, 1998, 1999, 2000, 2002, 2003, 2004, 2005, 2006 Free Software
+Foundation, Inc.
+
+     Permission is granted to copy, distribute and/or modify this
+     document under the terms of the GNU Free Documentation License,
+     Version 1.2 or any later version published by the Free Software
+     Foundation; with no Invariant Sections, with the Front-Cover Texts
+     being "A GNU Manual," and with the Back-Cover Texts as in (a)
+     below.  A copy of the license is included in the section entitled
+     "GNU Free Documentation License."
+
+     (a) The FSF's Back-Cover Text is: "You have freedom to copy and
+     modify this GNU Manual, like GNU software.  Copies published by
+     the Free Software Foundation raise funds for GNU development."
 
 INFO-DIR-SECTION GNU Packages
@@ -6 +29 @@
 END-INFO-DIR-ENTRY
 
-   This file documents the GNU Make utility, which determines
-automatically which pieces of a large program need to be recompiled,
-and issues the commands to recompile them.
-
-   This is Edition 0.61, last updated 02 May 2003, of `The GNU Make
-Manual', for `make', Version 3.81.
-
-   Copyright 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1997,
-1998, 1999, 2000, 2002, 2003, 2004 Free Software Foundation, Inc.
-
-   Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.1 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
-Texts.  A copy of the license is included in the section entitled "GNU
-Free Documentation License".
+
+File: make.info,  Node: Pattern Rules,  Next: Last Resort,  Prev: Chained Rules,  Up: Implicit Rules
+
+10.5 Defining and Redefining Pattern Rules
+==========================================
+
+You define an implicit rule by writing a "pattern rule".  A pattern
+rule looks like an ordinary rule, except that its target contains the
+character `%' (exactly one of them).  The target is considered a
+pattern for matching file names; the `%' can match any nonempty
+substring, while other characters match only themselves.  The
+prerequisites likewise use `%' to show how their names relate to the
+target name.
+
+   Thus, a pattern rule `%.o : %.c' says how to make any file `STEM.o'
+from another file `STEM.c'.
+
+   Note that expansion using `%' in pattern rules occurs *after* any
+variable or function expansions, which take place when the makefile is
+read.  *Note How to Use Variables: Using Variables, and *Note Functions
+for Transforming Text: Functions.
+
+* Menu:
+
+* Pattern Intro::               An introduction to pattern rules.
+* Pattern Examples::            Examples of pattern rules.
+* Automatic Variables::         How to use automatic variables in the
+                                  commands of implicit rules.
+* Pattern Match::               How patterns match.
+* Match-Anything Rules::        Precautions you should take prior to
+                                  defining rules that can match any
+                                  target file whatever.
+* Canceling Rules::             How to override or cancel built-in rules.
+
+
+File: make.info,  Node: Pattern Intro,  Next: Pattern Examples,  Prev: Pattern Rules,  Up: Pattern Rules
+
+10.5.1 Introduction to Pattern Rules
+------------------------------------
+
+A pattern rule contains the character `%' (exactly one of them) in the
+target; otherwise, it looks exactly like an ordinary rule.  The target
+is a pattern for matching file names; the `%' matches any nonempty
+substring, while other characters match only themselves.  
+
+   For example, `%.c' as a pattern matches any file name that ends in
+`.c'.  `s.%.c' as a pattern matches any file name that starts with
+`s.', ends in `.c' and is at least five characters long.  (There must
+be at least one character to match the `%'.)  The substring that the
+`%' matches is called the "stem".
+
+   `%' in a prerequisite of a pattern rule stands for the same stem
+that was matched by the `%' in the target.  In order for the pattern
+rule to apply, its target pattern must match the file name under
+consideration and all of its prerequisites (after pattern substitution)
+must name files that exist or can be made.  These files become
+prerequisites of the target.  
+
+   Thus, a rule of the form
+
+     %.o : %.c ; COMMAND...
+
+specifies how to make a file `N.o', with another file `N.c' as its
+prerequisite, provided that `N.c' exists or can be made.
+
+   There may also be prerequisites that do not use `%'; such a
+prerequisite attaches to every file made by this pattern rule.  These
+unvarying prerequisites are useful occasionally.
+
+   A pattern rule need not have any prerequisites that contain `%', or
+in fact any prerequisites at all.  Such a rule is effectively a general
+wildcard.  It provides a way to make any file that matches the target
+pattern.  *Note Last Resort::.
+
+   Pattern rules may have more than one target.  Unlike normal rules,
+this does not act as many different rules with the same prerequisites
+and commands.  If a pattern rule has multiple targets, `make' knows that
+the rule's commands are responsible for making all of the targets.  The
+commands are executed only once to make all the targets.  When searching
+for a pattern rule to match a target, the target patterns of a rule
+other than the one that matches the target in need of a rule are
+incidental: `make' worries only about giving commands and prerequisites
+to the file presently in question.  However, when this file's commands
+are run, the other targets are marked as having been updated themselves.  
+
+   The order in which pattern rules appear in the makefile is important
+since this is the order in which they are considered.  Of equally
+applicable rules, only the first one found is used.  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.  
+
+
+File: make.info,  Node: Pattern Examples,  Next: Automatic Variables,  Prev: Pattern Intro,  Up: Pattern Rules
+
+10.5.2 Pattern Rule Examples
+----------------------------
+
+Here are some examples of pattern rules actually predefined in `make'.
+First, the rule that compiles `.c' files into `.o' files:
+
+     %.o : %.c
+             $(CC) -c $(CFLAGS) $(CPPFLAGS) $< -o $@
+
+defines a rule that can make any file `X.o' from `X.c'.  The command
+uses the automatic variables `$@' and `$<' to substitute the names of
+the target file and the source file in each case where the rule applies
+(*note Automatic Variables::).
+
+   Here is a second built-in rule:
+
+     % :: RCS/%,v
+             $(CO) $(COFLAGS) $<
+
+defines a rule that can make any file `X' whatsoever from a
+corresponding file `X,v' in the subdirectory `RCS'.  Since the target
+is `%', this rule will apply to any file whatever, provided the
+appropriate prerequisite file exists.  The double colon makes the rule
+"terminal", which means that its prerequisite may not be an intermediate
+file (*note Match-Anything Pattern Rules: Match-Anything Rules.).
+
+   This pattern rule has two targets:
+
+     %.tab.c %.tab.h: %.y
+             bison -d $<
+
+This tells `make' that the command `bison -d X.y' will make both
+`X.tab.c' and `X.tab.h'.  If the file `foo' depends on the files
+`parse.tab.o' and `scan.o' and the file `scan.o' depends on the file
+`parse.tab.h', when `parse.y' is changed, the command `bison -d parse.y'
+will be executed only once, and the prerequisites of both `parse.tab.o'
+and `scan.o' will be satisfied.  (Presumably the file `parse.tab.o'
+will be recompiled from `parse.tab.c' and the file `scan.o' from
+`scan.c', while `foo' is linked from `parse.tab.o', `scan.o', and its
+other prerequisites, and it will execute happily ever after.)
+
+
+File: make.info,  Node: Automatic Variables,  Next: Pattern Match,  Prev: Pattern Examples,  Up: Pattern Rules
+
+10.5.3 Automatic Variables
+--------------------------
+
+Suppose you are writing a pattern rule to compile a `.c' file into a
+`.o' file: how do you write the `cc' command so that it operates on the
+right source file name?  You cannot write the name in the command,
+because the name is different each time the implicit rule is applied.
+
+   What you do is use a special feature of `make', the "automatic
+variables".  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 `$@' for the object file name and `$<'
+for the source file name.
+
+   It's very important that you recognize the limited scope in which
+automatic variable values are available: they only have values within
+the command script.  In particular, you cannot use them anywhere within
+the target list of a rule; they have no value there and will expand to
+the empty string.  Also, they cannot be accessed directly within the
+prerequisite list of a rule.  A common mistake is attempting to use
+`$@' within the prerequisites list; this will not work.  However, there
+is a special feature of GNU `make', secondary expansion (*note
+Secondary Expansion::), which will allow automatic variable values to
+be used in prerequisite lists.
+
+   Here is a table of automatic variables:
+
+`$@'
+     The file name of the target of the rule.  If the target is an
+     archive member, then `$@' is the name of the archive file.  In a
+     pattern rule that has multiple targets (*note Introduction to
+     Pattern Rules: Pattern Intro.), `$@' is the name of whichever
+     target caused the rule's commands to be run.
+
+`$%'
+     The target member name, when the target is an archive member.
+     *Note Archives::.  For example, if the target is `foo.a(bar.o)'
+     then `$%' is `bar.o' and `$@' is `foo.a'.  `$%' is empty when the
+     target is not an archive member.
+
+`$<'
+     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 implicit rule (*note Implicit Rules::).
+
+`$?'
+     The names of all the prerequisites that are newer than the target,
+     with spaces between them.  For prerequisites which are archive
+     members, only the member named is used (*note Archives::).  
+
+`$^'
+     The names of all the prerequisites, with spaces between them.  For
+     prerequisites which are archive members, only the member named is
+     used (*note Archives::).  A target has only one prerequisite on
+     each other file it depends on, no matter how many times each file
+     is listed as a prerequisite.  So if you list a prerequisite more
+     than once for a target, the value of `$^' contains just one copy
+     of the name.  This list does *not* contain any of the order-only
+     prerequisites; for those see the `$|' variable, below.  
+
+`$+'
+     This is like `$^', but prerequisites listed more than once are
+     duplicated in the order they were listed in the makefile.  This is
+     primarily useful for use in linking commands where it is
+     meaningful to repeat library file names in a particular order.
+
+`$|'
+     The names of all the order-only prerequisites, with spaces between
+     them.
+
+`$*'
+     The stem with which an implicit rule matches (*note How Patterns
+     Match: Pattern Match.).  If the target is `dir/a.foo.b' and the
+     target pattern is `a.%.b' then the stem is `dir/foo'.  The stem is
+     useful for constructing names of related files.  
+
+     In a static pattern rule, the stem is part of the file name that
+     matched the `%' in the target pattern.
+
+     In an explicit rule, there is no stem; so `$*' cannot be determined
+     in that way.  Instead, if the target name ends with a recognized
+     suffix (*note Old-Fashioned Suffix Rules: Suffix Rules.), `$*' is
+     set to the target name minus the suffix.  For example, if the
+     target name is `foo.c', then `$*' is set to `foo', since `.c' is a
+     suffix.  GNU `make' does this bizarre thing only for compatibility
+     with other implementations of `make'.  You should generally avoid
+     using `$*' except in implicit rules or static pattern rules.
+
+     If the target name in an explicit rule does not end with a
+     recognized suffix, `$*' is set to the empty string for that rule.
+
+   `$?' is useful even in explicit rules when you wish to operate on
+only the prerequisites that have changed.  For example, suppose that an
+archive named `lib' is supposed to contain copies of several object
+files.  This rule copies just the changed object files into the archive:
+
+     lib: foo.o bar.o lose.o win.o
+             ar r lib $?
+
+   Of the variables listed above, four have values that are single file
+names, and three have values that are lists of file names.  These seven
+have variants that get just the file's directory name or just the file
+name within the directory.  The variant variables' names are formed by
+appending `D' or `F', respectively.  These variants are semi-obsolete
+in GNU `make' since the functions `dir' and `notdir' can be used to get
+a similar effect (*note Functions for File Names: File Name
+Functions.).  Note, however, that the `D' variants all omit the
+trailing slash which always appears in the output of the `dir'
+function.  Here is a table of the variants:
+
+`$(@D)'
+     The directory part of the file name of the target, with the
+     trailing slash removed.  If the value of `$@' is `dir/foo.o' then
+     `$(@D)' is `dir'.  This value is `.' if `$@' does not contain a
+     slash.
+
+`$(@F)'
+     The file-within-directory part of the file name of the target.  If
+     the value of `$@' is `dir/foo.o' then `$(@F)' is `foo.o'.  `$(@F)'
+     is equivalent to `$(notdir $@)'.
+
+`$(*D)'
+`$(*F)'
+     The directory part and the file-within-directory part of the stem;
+     `dir' and `foo' in this example.
+
+`$(%D)'
+`$(%F)'
+     The directory part and the file-within-directory part of the target
+     archive member name.  This makes sense only for archive member
+     targets of the form `ARCHIVE(MEMBER)' and is useful only when
+     MEMBER may contain a directory name.  (*Note Archive Members as
+     Targets: Archive Members.)
+
+`$(<D)'
+`$(<F)'
+     The directory part and the file-within-directory part of the first
+     prerequisite.
+
+`$(^D)'
+`$(^F)'
+     Lists of the directory parts and the file-within-directory parts
+     of all prerequisites.
+
+`$(+D)'
+`$(+F)'
+     Lists of the directory parts and the file-within-directory parts
+     of all prerequisites, including multiple instances of duplicated
+     prerequisites.
+
+`$(?D)'
+`$(?F)'
+     Lists of the directory parts and the file-within-directory parts of
+     all prerequisites that are newer than the target.
+
+   Note that we use a special stylistic convention when we talk about
+these automatic variables; we write "the value of `$<'", rather than
+"the variable `<'" as we would write for ordinary variables such as
+`objects' and `CFLAGS'.  We think this convention looks more natural in
+this special case.  Please do not assume it has a deep significance;
+`$<' refers to the variable named `<' just as `$(CFLAGS)' refers to the
+variable named `CFLAGS'.  You could just as well use `$(<)' in place of
+`$<'.
+
+
+File: make.info,  Node: Pattern Match,  Next: Match-Anything Rules,  Prev: Automatic Variables,  Up: Pattern Rules
+
+10.5.4 How Patterns Match
+-------------------------
+
+A target pattern is composed of a `%' between a prefix and a suffix,
+either or both of which may be empty.  The pattern matches a file name
+only if the file name starts with the prefix and ends with the suffix,
+without overlap.  The text between the prefix and the suffix is called
+the "stem".  Thus, when the pattern `%.o' matches the file name
+`test.o', the stem is `test'.  The pattern rule prerequisites are
+turned into actual file names by substituting the stem for the character
+`%'.  Thus, if in the same example one of the prerequisites is written
+as `%.c', it expands to `test.c'.
+
+   When the target pattern does not contain a slash (and it usually does
+not), directory names in the file names are removed from the file name
+before it is compared with the target prefix and suffix.  After the
+comparison of the file name to the target pattern, the directory names,
+along with the slash that ends them, are added on to the prerequisite
+file names generated from the pattern rule's prerequisite patterns and
+the file name.  The directories are ignored only for the purpose of
+finding an implicit rule to use, not in the application of that rule.
+Thus, `e%t' matches the file name `src/eat', with `src/a' as the stem.
+When prerequisites are turned into file names, the directories from the
+stem are added at the front, while the rest of the stem is substituted
+for the `%'.  The stem `src/a' with a prerequisite pattern `c%r' gives
+the file name `src/car'.
+
+
+File: make.info,  Node: Match-Anything Rules,  Next: Canceling Rules,  Prev: Pattern Match,  Up: Pattern Rules
+
+10.5.5 Match-Anything Pattern Rules
+-----------------------------------
+
+When a pattern rule's target is just `%', it matches any file name
+whatever.  We call these rules "match-anything" rules.  They are very
+useful, but it can take a lot of time for `make' to think about them,
+because it must consider every such rule for each file name listed
+either as a target or as a prerequisite.
+
+   Suppose the makefile mentions `foo.c'.  For this target, `make'
+would have to consider making it by linking an object file `foo.c.o',
+or by C compilation-and-linking in one step from `foo.c.c', or by
+Pascal compilation-and-linking from `foo.c.p', and many other
+possibilities.
+
+   We know these possibilities are ridiculous since `foo.c' is a C
+source file, not an executable.  If `make' did consider these
+possibilities, it would ultimately reject them, because files such as
+`foo.c.o' and `foo.c.p' would not exist.  But these possibilities are so
+numerous that `make' would run very slowly if it had to consider them.
+
+   To gain speed, we have put various constraints on the way `make'
+considers match-anything rules.  There are two different constraints
+that can be applied, and each time you define a match-anything rule you
+must choose one or the other for that rule.
+
+   One choice is to mark the match-anything rule as "terminal" by
+defining it with a double colon.  When a rule is terminal, it does not
+apply unless its prerequisites actually exist.  Prerequisites that
+could be made with other implicit rules are not good enough.  In other
+words, no further chaining is allowed beyond a terminal rule.
+
+   For example, the built-in implicit rules for extracting sources from
+RCS and SCCS files are terminal; as a result, if the file `foo.c,v' does
+not exist, `make' will not even consider trying to make it as an
+intermediate file from `foo.c,v.o' or from `RCS/SCCS/s.foo.c,v'.  RCS
+and SCCS files are generally ultimate source files, which should not be
+remade from any other files; therefore, `make' can save time by not
+looking for ways to remake them.
+
+   If you do not mark the match-anything rule as terminal, then it is
+nonterminal.  A nonterminal match-anything rule cannot apply to a file
+name that indicates a specific type of data.  A file name indicates a
+specific type of data if some non-match-anything implicit rule target
+matches it.
+
+   For example, the file name `foo.c' matches the target for the pattern
+rule `%.c : %.y' (the rule to run Yacc).  Regardless of whether this
+rule is actually applicable (which happens only if there is a file
+`foo.y'), the fact that its target matches is enough to prevent
+consideration of any nonterminal match-anything rules for the file
+`foo.c'.  Thus, `make' will not even consider trying to make `foo.c' as
+an executable file from `foo.c.o', `foo.c.c', `foo.c.p', etc.
+
+   The motivation for this constraint is that nonterminal match-anything
+rules are used for making files containing specific types of data (such
+as executable files) and a file name with a recognized suffix indicates
+some other specific type of data (such as a C source file).
+
+   Special built-in dummy pattern rules are provided solely to recognize
+certain file names so that nonterminal match-anything rules will not be
+considered.  These dummy rules have no prerequisites and no commands,
+and they are ignored for all other purposes.  For example, the built-in
+implicit rule
+
+     %.p :
+
+exists to make sure that Pascal source files such as `foo.p' match a
+specific target pattern and thereby prevent time from being wasted
+looking for `foo.p.o' or `foo.p.c'.
+
+   Dummy pattern rules such as the one for `%.p' are made for every
+suffix listed as valid for use in suffix rules (*note Old-Fashioned
+Suffix Rules: Suffix Rules.).
+
+
+File: make.info,  Node: Canceling Rules,  Prev: Match-Anything Rules,  Up: Pattern Rules
+
+10.5.6 Canceling Implicit Rules
+-------------------------------
+
+You can override a built-in implicit rule (or one you have defined
+yourself) by defining a new pattern rule with the same target and
+prerequisites, but different commands.  When the new rule is defined,
+the built-in one is replaced.  The new rule's position in the sequence
+of implicit rules is determined by where you write the new rule.
+
+   You can cancel a built-in implicit rule by defining a pattern rule
+with the same target and prerequisites, but no commands.  For example,
+the following would cancel the rule that runs the assembler:
+
+     %.o : %.s
+
+
+File: make.info,  Node: Last Resort,  Next: Suffix Rules,  Prev: Pattern Rules,  Up: Implicit Rules
+
+10.6 Defining Last-Resort Default Rules
+=======================================
+
+You can define a last-resort implicit rule by writing a terminal
+match-anything pattern rule with no prerequisites (*note Match-Anything
+Rules::).  This is just like any other pattern rule; the only thing
+special about it is that it will match any target.  So such a rule's
+commands are used for all targets and prerequisites that have no
+commands of their own and for which no other implicit rule applies.
+
+   For example, when testing a makefile, you might not care if the
+source files contain real data, only that they exist.  Then you might
+do this:
+
+     %::
+             touch $@
+
+to cause all the source files needed (as prerequisites) to be created
+automatically.
+
+   You can instead define commands to be used for targets for which
+there are no rules at all, even ones which don't specify commands.  You
+do this by writing a rule for the target `.DEFAULT'.  Such a rule's
+commands are used for all prerequisites which do not appear as targets
+in any explicit rule, and for which no implicit rule applies.
+Naturally, there is no `.DEFAULT' rule unless you write one.
+
+   If you use `.DEFAULT' with no commands or prerequisites:
+
+     .DEFAULT:
+
+the commands previously stored for `.DEFAULT' are cleared.  Then `make'
+acts as if you had never defined `.DEFAULT' at all.
+
+   If you do not want a target to get the commands from a match-anything
+pattern rule or `.DEFAULT', but you also do not want any commands to be
+run for the target, you can give it empty commands (*note Defining
+Empty Commands: Empty Commands.).
+
+   You can use a last-resort rule to override part of another makefile.
+*Note Overriding Part of Another Makefile: Overriding Makefiles.
+
+
+File: make.info,  Node: Suffix Rules,  Next: Implicit Rule Search,  Prev: Last Resort,  Up: Implicit Rules
+
+10.7 Old-Fashioned Suffix Rules
+===============================
+
+"Suffix rules" are the old-fashioned way of defining implicit rules for
+`make'.  Suffix rules are obsolete because pattern rules are more
+general and clearer.  They are supported in GNU `make' for
+compatibility with old makefiles.  They come in two kinds:
+"double-suffix" and "single-suffix".
+
+   A double-suffix rule is defined by a pair of suffixes: the target
+suffix and the source suffix.  It matches any file whose name ends with
+the target suffix.  The corresponding implicit prerequisite is made by
+replacing the target suffix with the source suffix in the file name.  A
+two-suffix rule whose target and source suffixes are `.o' and `.c' is
+equivalent to the pattern rule `%.o : %.c'.
+
+   A single-suffix rule is defined by a single suffix, which is the
+source suffix.  It matches any file name, and the corresponding implicit
+prerequisite name is made by appending the source suffix.  A
+single-suffix rule whose source suffix is `.c' is equivalent to the
+pattern rule `% : %.c'.
+
+   Suffix rule definitions are recognized by comparing each rule's
+target against a defined list of known suffixes.  When `make' sees a
+rule whose target is a known suffix, this rule is considered a
+single-suffix rule.  When `make' sees a rule whose target is two known
+suffixes concatenated, this rule is taken as a double-suffix rule.
+
+   For example, `.c' and `.o' are both on the default list of known
+suffixes.  Therefore, if you define a rule whose target is `.c.o',
+`make' takes it to be a double-suffix rule with source suffix `.c' and
+target suffix `.o'.  Here is the old-fashioned way to define the rule
+for compiling a C source file:
+
+     .c.o:
+             $(CC) -c $(CFLAGS) $(CPPFLAGS) -o $@ $<
+
+   Suffix rules cannot have any prerequisites of their own.  If they
+have any, they are treated as normal files with funny names, not as
+suffix rules.  Thus, the rule:
+
+     .c.o: foo.h
+             $(CC) -c $(CFLAGS) $(CPPFLAGS) -o $@ $<
+
+tells how to make the file `.c.o' from the prerequisite file `foo.h',
+and is not at all like the pattern rule:
+
+     %.o: %.c foo.h
+             $(CC) -c $(CFLAGS) $(CPPFLAGS) -o $@ $<
+
+which tells how to make `.o' files from `.c' files, and makes all `.o'
+files using this pattern rule also depend on `foo.h'.
+
+   Suffix rules with no commands are also meaningless.  They do not
+remove previous rules as do pattern rules with no commands (*note
+Canceling Implicit Rules: Canceling Rules.).  They simply enter the
+suffix or pair of suffixes concatenated as a target in the data base.
+
+   The known suffixes are simply the names of the prerequisites of the
+special target `.SUFFIXES'.  You can add your own suffixes by writing a
+rule for `.SUFFIXES' that adds more prerequisites, as in:
+
+     .SUFFIXES: .hack .win
+
+which adds `.hack' and `.win' to the end of the list of suffixes.
+
+   If you wish to eliminate the default known suffixes instead of just
+adding to them, write a rule for `.SUFFIXES' with no prerequisites.  By
+special dispensation, this eliminates all existing prerequisites of
+`.SUFFIXES'.  You can then write another rule to add the suffixes you
+want.  For example,
+
+     .SUFFIXES:            # Delete the default suffixes
+     .SUFFIXES: .c .o .h   # Define our suffix list
+
+   The `-r' or `--no-builtin-rules' flag causes the default list of
+suffixes to be empty.
+
+   The variable `SUFFIXES' is defined to the default list of suffixes
+before `make' reads any makefiles.  You can change the list of suffixes
+with a rule for the special target `.SUFFIXES', but that does not alter
+this variable.
 
 
 File: make.info,  Node: Implicit Rule Search,  Prev: Suffix Rules,  Up: Implicit Rules
 
-Implicit Rule Search Algorithm
-==============================
+10.8 Implicit Rule Search Algorithm
+===================================
 
 Here is the procedure `make' uses for searching for an implicit rule
@@ -109 +676 @@
 File: make.info,  Node: Archives,  Next: Features,  Prev: Implicit Rules,  Up: Top
 
-Using `make' to Update Archive Files
-************************************
+11 Using `make' to Update Archive Files
+***************************************
 
 "Archive files" are files containing named subfiles called "members";
@@ -127 +694 @@
 File: make.info,  Node: Archive Members,  Next: Archive Update,  Prev: Archives,  Up: Archives
 
-Archive Members as Targets
-==========================
+11.1 Archive Members as Targets
+===============================
 
 An individual member of an archive file can be used as a target or
@@ -148 +715 @@
 
    In fact, nearly all archive member targets are updated in just this
-way and there is an implicit rule to do it for you.  *Note:* The `c'
-flag to `ar' is required if the archive file does not already exist.
+way and there is an implicit rule to do it for you.  *Please note:* The
+`c' flag to `ar' is required if the archive file does not already exist.
 
    To specify several members in the same archive, you can write all the
@@ -169 +736 @@
 File: make.info,  Node: Archive Update,  Next: Archive Pitfalls,  Prev: Archive Members,  Up: Archives
 
-Implicit Rule for Archive Member Targets
-========================================
+11.2 Implicit Rule for Archive Member Targets
+=============================================
 
 Recall that a target that looks like `A(M)' stands for the member named
@@ -219 +786 @@
 File: make.info,  Node: Archive Symbols,  Prev: Archive Update,  Up: Archive Update
 
-Updating Archive Symbol Directories
------------------------------------
+11.2.1 Updating Archive Symbol Directories
+------------------------------------------
 
 An archive file that is used as a library usually contains a special
@@ -250 +817 @@
 File: make.info,  Node: Archive Pitfalls,  Next: Archive Suffix Rules,  Prev: Archive Update,  Up: Archives
 
-Dangers When Using Archives
-===========================
+11.3 Dangers When Using Archives
+================================
 
 It is important to be careful when using parallel execution (the `-j'
@@ -266 +833 @@
 File: make.info,  Node: Archive Suffix Rules,  Prev: Archive Pitfalls,  Up: Archives
 
-Suffix Rules for Archive Files
-==============================
+11.4 Suffix Rules for Archive Files
+===================================
 
 You can write a special kind of suffix rule for dealing with archive
@@ -305 +872 @@
 File: make.info,  Node: Features,  Next: Missing,  Prev: Archives,  Up: Top
 
-Features of GNU `make'
-**********************
+12 Features of GNU `make'
+*************************
 
 Here is a summary of the features of GNU `make', for comparison with
@@ -499 +1066 @@
 
    * The built-in variable `MAKE_VERSION' gives the version number of
-     `make'.
+     `make'.  
 
 
 File: make.info,  Node: Missing,  Next: Makefile Conventions,  Prev: Features,  Up: Top
 
-Incompatibilities and Missing Features
-**************************************
+13 Incompatibilities and Missing Features
+*****************************************
 
 The `make' programs in various other systems support a few features
@@ -545 +1112 @@
      imagine what went on in the minds of Unix `make' developers to do
      this; it is utterly inconsistent with the normal definition of
-     `$*'.
+     `$*'.  
 
    * In some Unix `make's, implicit rule search (*note Using Implicit
@@ -589 +1156 @@
 File: make.info,  Node: Makefile Conventions,  Next: Quick Reference,  Prev: Missing,  Up: Top
 
-Makefile Conventions
-********************
+14 Makefile Conventions
+***********************
 
 This node describes conventions for writing the Makefiles for GNU
@@ -609 +1176 @@
 File: make.info,  Node: Makefile Basics,  Next: Utilities in Makefiles,  Up: Makefile Conventions
 
-General Conventions for Makefiles
-=================================
+14.1 General Conventions for Makefiles
+======================================
 
 Every Makefile should contain this line:
@@ -689 +1256 @@
 File: make.info,  Node: Utilities in Makefiles,  Next: Command Variables,  Prev: Makefile Basics,  Up: Makefile Conventions
 
-Utilities in Makefiles
-======================
+14.2 Utilities in Makefiles
+===========================
 
 Write the Makefile commands (and any shell scripts, such as
@@ -744 +1311 @@
 File: make.info,  Node: Command Variables,  Next: Directory Variables,  Prev: Utilities in Makefiles,  Up: Makefile Conventions
 
-Variables for Specifying Commands
-=================================
+14.3 Variables for Specifying Commands
+======================================
 
 Makefiles should provide variables for overriding certain commands,
@@ -824 +1391 @@
 File: make.info,  Node: Directory Variables,  Next: Standard Targets,  Prev: Command Variables,  Up: Makefile Conventions
 
-Variables for Installation Directories
-======================================
+14.4 Variables for Installation Directories
+===========================================
 
 Installation directories should always be named by variables, so it is
 easy to install in a nonstandard place.  The standard names for these
-variables are described below.  They are based on a standard filesystem
-layout; variants of it are used in SVR4, 4.4BSD, GNU/Linux, Ultrix v4,
-and other modern operating systems.
+variables and the values they should have in GNU packages are described
+below.  They are based on a standard filesystem layout; variants of it
+are used in GNU/Linux and other modern operating systems.
+
+   Installers are expected to override these values when calling `make'
+(e.g., `make prefix=/usr install' or `configure' (e.g., `configure
+--prefix=/usr').  GNU packages should not try to guess which value
+should be appropriate for these variables on the system they are being
+installed onto: use the default settings specified here so that all GNU
+packages behave identically, allowing the installer to achieve any
+desired layout.
 
    These two variables set the root for the installation.  All the other
@@ -884 +1459 @@
      (If you are using Autoconf, write it as `@libexecdir@'.)
 
+     The definition of `libexecdir' is the same for all packages, so
+     you should install your data in a subdirectory thereof.  Most
+     packages install their data under `$(libexecdir)/PACKAGE-NAME/',
+     possibly within additional subdirectories thereof, such as
+     `$(libexecdir)/PACKAGE-NAME/MACHINE/VERSION'.
+
    Data files used by the program during its execution are divided into
 categories in two ways.
@@ -900 +1481 @@
 architecture-independent, and it is generally not hard.
 
-   Therefore, here are the variables Makefiles should use to specify
-directories:
+   Here are the variables Makefiles should use to specify directories
+to put these various kinds of files in:
+
+`datarootdir'
+     The root of the directory tree for read-only
+     architecture-independent data files.  This should normally be
+     `/usr/local/share', but write it as `$(prefix)/share'.  (If you
+     are using Autoconf, write it as `@datarootdir@'.)  `datadir''s
+     default value is based on this variable; so are `infodir',
+     `mandir', and others.
 
 `datadir'
-     The directory for installing read-only architecture independent
-     data files.  This should normally be `/usr/local/share', but write
-     it as `$(prefix)/share'.  (If you are using Autoconf, write it as
-     `@datadir@'.)  As a special exception, see `$(infodir)' and
-     `$(includedir)' below.
+     The directory for installing idiosyncratic read-only
+     architecture-independent data files for this program.  This is
+     usually the same place as `datarootdir', but we use the two
+     separate variables so that you can move these program-specific
+     files without altering the location for Info files, man pages, etc.
+
+     This should normally be `/usr/local/share', but write it as
+     `$(datarootdir)'.  (If you are using Autoconf, write it as
+     `@datadir@'.)
+
+     The definition of `datadir' is the same for all packages, so you
+     should install your data in a subdirectory thereof.  Most packages
+     install their data under `$(datadir)/PACKAGE-NAME/'.
 
 `sysconfdir'
@@ -941 +1538 @@
      `@localstatedir@'.)
 
-`libdir'
-     The directory for object files and libraries of object code.  Do
-     not install executables here, they probably ought to go in
-     `$(libexecdir)' instead.  The value of `libdir' should normally be
-     `/usr/local/lib', but write it as `$(exec_prefix)/lib'.  (If you
-     are using Autoconf, write it as `@libdir@'.)
-
-`infodir'
-     The directory for installing the Info files for this package.  By
-     default, it should be `/usr/local/info', but it should be written
-     as `$(prefix)/info'.  (If you are using Autoconf, write it as
-     `@infodir@'.)
-
-`lispdir'
-     The directory for installing any Emacs Lisp files in this package.
-     By default, it should be `/usr/local/share/emacs/site-lisp', but
-     it should be written as `$(prefix)/share/emacs/site-lisp'.
-
-     If you are using Autoconf, write the default as `@lispdir@'.  In
-     order to make `@lispdir@' work, you need the following lines in
-     your `configure.in' file:
-
-          lispdir='${datadir}/emacs/site-lisp'
-          AC_SUBST(lispdir)
+   These variables specify the directory for installing certain specific
+types of files, if your program has them.  Every GNU package should
+have Info files, so every program needs `infodir', but not all need
+`libdir' or `lispdir'.
 
 `includedir'
@@ -1000 +1577 @@
      string in the file--part of a comment--and `grep' for that string.
 
+`docdir'
+     The directory for installing documentation files (other than Info)
+     for this package.  By default, it should be
+     `/usr/local/share/doc/YOURPKG', but it should be written as
+     `$(datarootdir)/doc/YOURPKG'.  (If you are using Autoconf, write
+     it as `@docdir@'.)  The YOURPKG subdirectory, which may include a
+     version number, prevents collisions among files with common names,
+     such as `README'.
+
+`infodir'
+     The directory for installing the Info files for this package.  By
+     default, it should be `/usr/local/share/info', but it should be
+     written as `$(datarootdir)/info'.  (If you are using Autoconf,
+     write it as `@infodir@'.)  `infodir' is separate from `docdir' for
+     compatibility with existing practice.
+
+`htmldir'
+`dvidir'
+`pdfdir'
+`psdir'
+     Directories for installing documentation files in the particular
+     format.  (It is not required to support documentation in all these
+     formats.)  They should all be set to `$(docdir)' by default.  (If
+     you are using Autoconf, write them as `@htmldir@', `@dvidir@',
+     etc.)  Packages which supply several translations of their
+     documentation should install them in `$(htmldir)/'LL,
+     `$(pdfdir)/'LL, etc. where LL is a locale abbreviation such as
+     `en' or `pt_BR'.
+
+`libdir'
+     The directory for object files and libraries of object code.  Do
+     not install executables here, they probably ought to go in
+     `$(libexecdir)' instead.  The value of `libdir' should normally be
+     `/usr/local/lib', but write it as `$(exec_prefix)/lib'.  (If you
+     are using Autoconf, write it as `@libdir@'.)
+
+`lispdir'
+     The directory for installing any Emacs Lisp files in this package.
+     By default, it should be `/usr/local/share/emacs/site-lisp', but
+     it should be written as `$(datarootdir)/emacs/site-lisp'.
+
+     If you are using Autoconf, write the default as `@lispdir@'.  In
+     order to make `@lispdir@' work, you need the following lines in
+     your `configure.in' file:
+
+          lispdir='${datarootdir}/emacs/site-lisp'
+          AC_SUBST(lispdir)
+
+`localedir'
+     The directory for installing locale-specific message catalogs for
+     this package.  By default, it should be `/usr/local/share/locale',
+     but it should be written as `$(datarootdir)/locale'.  (If you are
+     using Autoconf, write it as `@localedir@'.)  This directory
+     usually has a subdirectory per locale.
+
    Unix-style man pages are installed in one of the following:
 
 `mandir'
      The top-level directory for installing the man pages (if any) for
-     this package.  It will normally be `/usr/local/man', but you should
-     write it as `$(prefix)/man'.  (If you are using Autoconf, write it
-     as `@mandir@'.)
+     this package.  It will normally be `/usr/local/share/man', but you
+     should write it as `$(datarootdir)/man'.  (If you are using
+     Autoconf, write it as `@mandir@'.)
 
 `man1dir'
@@ -1049 +1681 @@
      # NOTE: This directory must exist when you start the install.
      prefix = /usr/local
+     datarootdir = $(prefix)/share
+     datadir = $(datarootdir)
      exec_prefix = $(prefix)
      # Where to put the executable for the command `gcc'.
@@ -1055 +1689 @@
      libexecdir = $(exec_prefix)/libexec
      # Where to put the Info files.
-     infodir = $(prefix)/info
+     infodir = $(datarootdir)/info
 
    If your program installs a large number of files into one of the
@@ -1072 +1706 @@
 File: make.info,  Node: Standard Targets,  Next: Install Command Categories,  Prev: Directory Variables,  Up: Makefile Conventions
 
-Standard Targets for Users
-==========================
+14.5 Standard Targets for Users
+===============================
 
 All GNU programs should have the following targets in their Makefiles:
@@ -1142 +1776 @@
      Categories::.
 
+`install-html'
+`install-dvi'
+`install-pdf'
+`install-ps'
+     These targets install documentation in formats other than Info;
+     they're intended to be called explicitly by the person installing
+     the package, if that format is desired.  GNU prefers Info files,
+     so these must be installed by the `install' target.
+
+     When you have many documentation files to install, we recommend
+     that you avoid collisions and clutter by arranging for these
+     targets to install in subdirectories of the appropriate
+     installation directory, such as `htmldir'.  As one example, if
+     your package has multiple manuals, and you wish to install HTML
+     documentation with many files (such as the "split" mode output by
+     `makeinfo --html'), you'll certainly want to use subdirectories,
+     or two nodes with the same name in different manuals will
+     overwrite each other.
+
 `uninstall'
-     Delete all the installed files--the copies that the `install'
-     target creates.
+     Delete all the installed files--the copies that the `install' and
+     `install-*' targets create.
 
      This rule should not modify the directories where compilation is
@@ -1176 +1829 @@
 
 `clean'
-     Delete all files from the current directory that are normally
-     created by building the program.  Don't delete the files that
-     record the configuration.  Also preserve files that could be made
-     by building, but normally aren't because the distribution comes
-     with them.
+     Delete all files in the current directory that are normally
+     created by building the program.  Also delete files in other
+     directories if they are created by this makefile.  However, don't
+     delete the files that record the configuration.  Also preserve
+     files that could be made by building, but normally aren't because
+     the distribution comes with them.  There is no need to delete
+     parent directories that were created with `mkdir -p', since they
+     could have existed anyway.
 
      Delete `.dvi' files here if they are not part of the distribution.
 
 `distclean'
-     Delete all files from the current directory that are created by
-     configuring or building the program.  If you have unpacked the
-     source and built the program without creating any other files,
-     `make distclean' should leave only the files that were in the
-     distribution.
+     Delete all files in the current directory (or created by this
+     makefile) that are created by configuring or building the program.
+     If you have unpacked the source and built the program without
+     creating any other files, `make distclean' should leave only the
+     files that were in the distribution.  However, there is no need to
+     delete parent directories that were created with `mkdir -p', since
+     they could have existed anyway.
 
 `mostlyclean'
@@ -1198 +1856 @@
 
 `maintainer-clean'
-     Delete almost everything from the current directory that can be
-     reconstructed with this Makefile.  This typically includes
-     everything deleted by `distclean', plus more: C source files
-     produced by Bison, tags tables, Info files, and so on.
+     Delete almost everything that can be reconstructed with this
+     Makefile.  This typically includes everything deleted by
+     `distclean', plus more: C source files produced by Bison, tags
+     tables, Info files, and so on.
 
      The reason we say "almost everything" is that running the command
@@ -1208 +1866 @@
      generally, `make maintainer-clean' should not delete anything that
      needs to exist in order to run `configure' and then begin to build
-     the program.  This is the only exception; `maintainer-clean' should
+     the program.  Also, there is no need to delete parent directories
+     that were created with `mkdir -p', since they could have existed
+     anyway.  These are the only exceptions; `maintainer-clean' should
      delete everything else that can be rebuilt.
 
@@ -1233 +1893 @@
 
           info: foo.info
-          
+
           foo.info: foo.texi chap1.texi chap2.texi
                   $(MAKEINFO) $(srcdir)/foo.texi
@@ -1248 +1908 @@
 
 `dvi'
-     Generate DVI files for all Texinfo documentation.  For example:
+`html'
+`pdf'
+`ps'
+     Generate documentation files in the given format, if possible.
+     Here's an example rule for generating DVI files from Texinfo:
 
           dvi: foo.dvi
-          
+
           foo.dvi: foo.texi chap1.texi chap2.texi
                   $(TEXI2DVI) $(srcdir)/foo.texi
@@ -1259 +1923 @@
      distribution.(1)  Alternatively, write just the dependencies, and
      allow GNU `make' to provide the command.
+
+     Here's another example, this one for generating HTML from Texinfo:
+
+          html: foo.html
+
+          foo.html: foo.texi chap1.texi chap2.texi
+                  $(TEXI2HTML) $(srcdir)/foo.texi
+
+     Again, you would define the variable `TEXI2HTML' in the Makefile;
+     for example, it might run `makeinfo --no-split --html' (`makeinfo'
+     is part of the Texinfo distribution).
 
 `dist'
@@ -1329 +2004 @@
 File: make.info,  Node: Install Command Categories,  Prev: Standard Targets,  Up: Makefile Conventions
 
-Install Command Categories
-==========================
+14.6 Install Command Categories
+===============================
 
 When writing the `install' target, you must classify all the commands
@@ -1415 +2090 @@
    Programs to build binary packages work by extracting the
 pre-installation and post-installation commands.  Here is one way of
-extracting the pre-installation commands:
-
-     make -n install -o all \
+extracting the pre-installation commands (the `-s' option to `make' is
+needed to silence messages about entering subdirectories):
+
+     make -s -n install -o all \
            PRE_INSTALL=pre-install \
            POST_INSTALL=post-install \
@@ -1425 +2101 @@
 where the file `pre-install.awk' could contain this:
 
-     $0 ~ /^\t[ \t]*(normal_install|post_install)[ \t]*$/ {on = 0}
+     $0 ~ /^(normal-install|post-install)[ \t]*$/ {on = 0}
      on {print $0}
-     $0 ~ /^\t[ \t]*pre_install[ \t]*$/ {on = 1}
-
-   The resulting file of pre-installation commands is executed as a
-shell script as part of installing the binary package.
+     $0 ~ /^pre-install[ \t]*$/ {on = 1}
 
 
 File: make.info,  Node: Quick Reference,  Next: Error Messages,  Prev: Makefile Conventions,  Up: Top
 
-Quick Reference
-***************
+Appendix A Quick Reference
+**************************
 
 This appendix summarizes the directives, text manipulation functions,
@@ -1504 +2177 @@
      directive.
 
-   Here is a summary of the text manipulation functions (*note
-Functions::):
+   Here is a summary of the built-in functions (*note Functions::):
 
 `$(subst FROM,TO,TEXT)'
@@ -1542 +2214 @@
      Functions.
 
+`$(word N,TEXT)'
+     Extract the Nth word (one-origin) of TEXT.
+     *Note Functions for String Substitution and Analysis: Text
+     Functions.
+
+`$(words TEXT)'
+     Count the number of words in TEXT.
+     *Note Functions for String Substitution and Analysis: Text
+     Functions.
+
+`$(wordlist S,E,TEXT)'
+     Returns the list of words in TEXT from S to E.
+     *Note Functions for String Substitution and Analysis: Text
+     Functions.
+
+`$(firstword NAMES...)'
+     Extract the first word of NAMES.
+     *Note Functions for String Substitution and Analysis: Text
+     Functions.
+
+`$(lastword NAMES...)'
+     Extract the last word of NAMES.
+     *Note Functions for String Substitution and Analysis: Text
+     Functions.
+
 `$(dir NAMES...)'
      Extract the directory part of each file name.
@@ -1571 +2268 @@
      *Note Functions for File Names: File Name Functions.
 
-`$(word N,TEXT)'
-     Extract the Nth word (one-origin) of TEXT.
-     *Note Functions for File Names: File Name Functions.
-
-`$(words TEXT)'
-     Count the number of words in TEXT.
-     *Note Functions for File Names: File Name Functions.
-
-`$(wordlist S,E,TEXT)'
-     Returns the list of words in TEXT from S to E.
-     *Note Functions for File Names: File Name Functions.
-
-`$(firstword NAMES...)'
-     Extract the first word of NAMES.
-     *Note Functions for File Names: File Name Functions.
-
 `$(wildcard PATTERN...)'
      Find file names matching a shell file name pattern (_not_ a `%'
@@ -1592 +2273 @@
      *Note The Function `wildcard': Wildcard Function.
 
+`$(realpath NAMES...)'
+     For each file name in NAMES, expand to an absolute name that does
+     not contain any `.', `..', nor symlinks.
+     *Note Functions for File Names: File Name Functions.
+
+`$(abspath NAMES...)'
+     For each file name in NAMES, expand to an absolute name that does
+     not contain any `.' or `..' components, but preserves symlinks.
+     *Note Functions for File Names: File Name Functions.
+
 `$(error TEXT...)'
      When this function is evaluated, `make' generates a fatal error
@@ -1610 +2301 @@
      defined.
      *Note The `origin' Function: Origin Function.
+
+`$(flavor VARIABLE)'
+     Return a string describing the flavor of the `make' variable
+     VARIABLE.
+     *Note The `flavor' Function: Flavor Function.
 
 `$(foreach VAR,WORDS,TEXT)'
@@ -1701 +2397 @@
      `/bin/sh'.  You can set `SHELL' in the makefile to change the
      shell used to run commands.  *Note Command Execution: Execution.
+     The `SHELL' variable is handled specially when importing from and
+     exporting to the environment.  *Note Choosing the Shell::.
 
 `MAKESHELL'
      On MS-DOS only, the name of the command interpreter that is to be
-     used by `make'. This value takes precedence over the value of
+     used by `make'.  This value takes precedence over the value of
      `SHELL'.  *Note MAKESHELL variable: Execution.
 
@@ -1748 +2446 @@
 File: make.info,  Node: Error Messages,  Next: Complex Makefile,  Prev: Quick Reference,  Up: Top
 
-Errors Generated by Make
-************************
+Appendix B Errors Generated by Make
+***********************************
 
 Here is a list of the more common errors you might see generated by
@@ -1822 +2520 @@
      on the command line, and `make' couldn't find any makefiles to
      read in.  The latter means that some makefile was found, but it
-     didn't contain any default target and none was given on the
-     command line.  GNU `make' has nothing to do in these situations.
-     *Note Arguments to Specify the Makefile: Makefile Arguments.
+     didn't contain any default goal and none was given on the command
+     line.  GNU `make' has nothing to do in these situations.  *Note
+     Arguments to Specify the Makefile: Makefile Arguments.
 
 `Makefile `XXX' was not found.'
@@ -1901 +2599 @@
 File: make.info,  Node: Complex Makefile,  Next: GNU Free Documentation License,  Prev: Error Messages,  Up: Top
 
-Complex Makefile Example
-************************
+Appendix C Complex Makefile Example
+***********************************
 
 Here is the makefile for the GNU `tar' program.  This is a moderately
@@ -1938 +2636 @@
      # Un*x Makefile for GNU tar program.
      # Copyright (C) 1991 Free Software Foundation, Inc.
-     
+
      # This program is free software; you can redistribute
      # it and/or modify it under the terms of the GNU
@@ -1944 +2642 @@
      ...
      ...
-     
+
      SHELL = /bin/sh
-     
+
      #### Start of system configuration section. ####
-     
+
      srcdir = .
-     
+
      # If you use gcc, you should either run the
      # fixincludes script that comes with it or else use
@@ -1959 +2657 @@
      INSTALL = /usr/local/bin/install -c
      INSTALLDATA = /usr/local/bin/install -c -m 644
-     
+
      # Things you might add to DEFS:
      # -DSTDC_HEADERS        If you have ANSI C headers and
@@ -2010 +2708 @@
      # -DXENIX               If you have sys/inode.h
      #                       and need it 94 to be included.
-     
+
      DEFS =  -DSIGTYPE=int -DDIRENT -DSTRSTR_MISSING \
              -DVPRINTF_MISSING -DBSD42
@@ -2019 +2717 @@
      DEF_AR_FILE = /dev/rmt8
      DEFBLOCKING = 20
-     
+
      CDEBUG = -g
      CFLAGS = $(CDEBUG) -I. -I$(srcdir) $(DEFS) \
@@ -2025 +2723 @@
              -DDEFBLOCKING=$(DEFBLOCKING)
      LDFLAGS = -g
-     
+
      prefix = /usr/local
      # Prefix for each installed program,
      # normally empty or `g'.
      binprefix =
-     
+
      # The directory to install tar in.
      bindir = $(prefix)/bin
-     
+
      # The directory to install the info files in.
      infodir = $(prefix)/info
-     
+
      #### End of system configuration section. ####
-     
+
      SRC1 =  tar.c create.c extract.c buffer.c \
              getoldopt.c update.c gnu.c mangle.c
@@ -2058 +2756 @@
              msd_dir.h msd_dir.c tcexparg.c \
              level-0 level-1 backup-specs testpad.c
-     
+
+     .PHONY: all
      all:    tar rmt tar.info
-     
+
+     .PHONY: tar
      tar:    $(OBJS)
              $(CC) $(LDFLAGS) -o $@ $(OBJS) $(LIBS)
-     
+
      rmt:    rmt.c
              $(CC) $(CFLAGS) $(LDFLAGS) -o $@ rmt.c
-     
+
      tar.info: tar.texinfo
              makeinfo tar.texinfo
-     
+
+     .PHONY: install
      install: all
              $(INSTALL) tar $(bindir)/$(binprefix)tar
              -test ! -f rmt || $(INSTALL) rmt /etc/rmt
              $(INSTALLDATA) $(srcdir)/tar.info* $(infodir)
-     
+
      $(OBJS): tar.h port.h testpad.h
      regex.o buffer.o tar.o: regex.h
      # getdate.y has 8 shift/reduce conflicts.
-     
+
      testpad.h: testpad
              ./testpad
-     
+
      testpad: testpad.o
              $(CC) -o $@ testpad.o
-     
+
      TAGS:   $(SRCS)
              etags $(SRCS)
-     
+
+     .PHONY: clean
      clean:
              rm -f *.o tar rmt testpad testpad.h core
-     
+
+     .PHONY: distclean
      distclean: clean
              rm -f TAGS Makefile config.status
-     
+
+     .PHONY: realclean
      realclean: distclean
              rm -f tar.info*
-     
+
+     .PHONY: shar
      shar: $(SRCS) $(AUX)
              shar $(SRCS) $(AUX) | compress \
@@ -2103 +2808 @@
                           -e q
                           version.c`.shar.Z
-     
+
+     .PHONY: dist
      dist: $(SRCS) $(AUX)
              echo tar-`sed \
@@ -2115 +2821 @@
              tar chZf `cat .fname`.tar.Z `cat .fname`
              -rm -rf `cat .fname` .fname
-     
+
      tar.zoo: $(SRCS) $(AUX)
              -rm -rf tmp.dir
@@ -2130 +2836 @@
 File: make.info,  Node: GNU Free Documentation License,  Next: Concept Index,  Prev: Complex Makefile,  Up: Top
 
-GNU Free Documentation License
-******************************
-
-                        Version 1.1, March 2000
-     Copyright (C) 2000 Free Software Foundation, Inc.
-     59 Temple Place, Suite 330, Boston, MA  02111-1307, USA
-     
+Appendix D GNU Free Documentation License
+*****************************************
+
+                      Version 1.2, November 2002
+
+     Copyright (C) 2000,2001,2002 Free Software Foundation, Inc.
+     51 Franklin St, Fifth Floor, Boston, MA  02110-1301, USA
+
      Everyone is permitted to copy and distribute verbatim copies
      of this license document, but changing it is not allowed.
@@ -2143 +2850 @@
 
      The purpose of this License is to make a manual, textbook, or other
-     written document "free" in the sense of freedom: to assure everyone
-     the effective freedom to copy and redistribute it, with or without
-     modifying it, either commercially or noncommercially.  Secondarily,
-     this License preserves for the author and publisher a way to get
-     credit for their work, while not being considered responsible for
-     modifications made by others.
+     functional and useful document "free" in the sense of freedom: to
+     assure everyone the effective freedom to copy and redistribute it,
+     with or without modifying it, either commercially or
+     noncommercially.  Secondarily, this License preserves for the
+     author and publisher a way to get credit for their work, while not
+     being considered responsible for modifications made by others.
 
      This License is a kind of "copyleft", which means that derivative
@@ -2166 +2873 @@
   1. APPLICABILITY AND DEFINITIONS
 
-     This License applies to any manual or other work that contains a
-     notice placed by the copyright holder saying it can be distributed
-     under the terms of this License.  The "Document", below, refers to
-     any such manual or work.  Any member of the public is a licensee,
-     and is addressed as "you".
+     This License applies to any manual or other work, in any medium,
+     that contains a notice placed by the copyright holder saying it
+     can be distributed under the terms of this License.  Such a notice
+     grants a world-wide, royalty-free license, unlimited in duration,
+     to use that work under the conditions stated herein.  The
+     "Document", below, refers to any such manual or work.  Any member
+     of the public is a licensee, and is addressed as "you".  You
+     accept the license if you copy, modify or distribute the work in a
+     way requiring permission under copyright law.
 
      A "Modified Version" of the Document means any work containing the
@@ -2176 +2887 @@
      modifications and/or translated into another language.
 
-     A "Secondary Section" is a named appendix or a front-matter
-     section of the Document that deals exclusively with the
-     relationship of the publishers or authors of the Document to the
-     Document's overall subject (or to related matters) and contains
-     nothing that could fall directly within that overall subject.
-     (For example, if the Document is in part a textbook of
-     mathematics, a Secondary Section may not explain any mathematics.)
-     The relationship could be a matter of historical connection with
-     the subject or with related matters, or of legal, commercial,
-     philosophical, ethical or political position regarding them.
+     A "Secondary Section" is a named appendix or a front-matter section
+     of the Document that deals exclusively with the relationship of the
+     publishers or authors of the Document to the Document's overall
+     subject (or to related matters) and contains nothing that could
+     fall directly within that overall subject.  (Thus, if the Document
+     is in part a textbook of mathematics, a Secondary Section may not
+     explain any mathematics.)  The relationship could be a matter of
+     historical connection with the subject or with related matters, or
+     of legal, commercial, philosophical, ethical or political position
+     regarding them.
 
      The "Invariant Sections" are certain Secondary Sections whose
      titles are designated, as being those of Invariant Sections, in
      the notice that says that the Document is released under this
-     License.
+     License.  If a section does not fit the above definition of
+     Secondary then it is not allowed to be designated as Invariant.
+     The Document may contain zero Invariant Sections.  If the Document
+     does not identify any Invariant Sections then there are none.
 
      The "Cover Texts" are certain short passages of text that are
      listed, as Front-Cover Texts or Back-Cover Texts, in the notice
-     that says that the Document is released under this License.
+     that says that the Document is released under this License.  A
+     Front-Cover Text may be at most 5 words, and a Back-Cover Text may
+     be at most 25 words.
 
      A "Transparent" copy of the Document means a machine-readable copy,
      represented in a format whose specification is available to the
-     general public, whose contents can be viewed and edited directly
-     and straightforwardly with generic text editors or (for images
+     general public, that is suitable for revising the document
+     straightforwardly with generic text editors or (for images
      composed of pixels) generic paint programs or (for drawings) some
      widely available drawing editor, and that is suitable for input to
      text formatters or for automatic translation to a variety of
      formats suitable for input to text formatters.  A copy made in an
-     otherwise Transparent file format whose markup has been designed
-     to thwart or discourage subsequent modification by readers is not
-     Transparent.  A copy that is not "Transparent" is called "Opaque".
+     otherwise Transparent file format whose markup, or absence of
+     markup, has been arranged to thwart or discourage subsequent
+     modification by readers is not Transparent.  An image format is
+     not Transparent if used for any substantial amount of text.  A
+     copy that is not "Transparent" is called "Opaque".
 
      Examples of suitable formats for Transparent copies include plain
      ASCII without markup, Texinfo input format, LaTeX input format,
      SGML or XML using a publicly available DTD, and
-     standard-conforming simple HTML designed for human modification.
-     Opaque formats include PostScript, PDF, proprietary formats that
-     can be read and edited only by proprietary word processors, SGML
-     or XML for which the DTD and/or processing tools are not generally
-     available, and the machine-generated HTML produced by some word
-     processors for output purposes only.
+     standard-conforming simple HTML, PostScript or PDF designed for
+     human modification.  Examples of transparent image formats include
+     PNG, XCF and JPG.  Opaque formats include proprietary formats that
+     can be read and edited only by proprietary word processors, SGML or
+     XML for which the DTD and/or processing tools are not generally
+     available, and the machine-generated HTML, PostScript or PDF
+     produced by some word processors for output purposes only.
 
      The "Title Page" means, for a printed book, the title page itself,
@@ -2224 +2943 @@
      Page" means the text near the most prominent appearance of the
      work's title, preceding the beginning of the body of the text.
+
+     A section "Entitled XYZ" means a named subunit of the Document
+     whose title either is precisely XYZ or contains XYZ in parentheses
+     following text that translates XYZ in another language.  (Here XYZ
+     stands for a specific section name mentioned below, such as
+     "Acknowledgements", "Dedications", "Endorsements", or "History".)
+     To "Preserve the Title" of such a section when you modify the
+     Document means that it remains a section "Entitled XYZ" according
+     to this definition.
+
+     The Document may include Warranty Disclaimers next to the notice
+     which states that this License applies to the Document.  These
+     Warranty Disclaimers are considered to be included by reference in
+     this License, but only as regards disclaiming warranties: any other
+     implication that these Warranty Disclaimers may have is void and
+     has no effect on the meaning of this License.
 
   2. VERBATIM COPYING
@@ -2243 +2978 @@
   3. COPYING IN QUANTITY
 
-     If you publish printed copies of the Document numbering more than
-     100, and the Document's license notice requires Cover Texts, you
-     must enclose the copies in covers that carry, clearly and legibly,
-     all these Cover Texts: Front-Cover Texts on the front cover, and
+     If you publish printed copies (or copies in media that commonly
+     have printed covers) of the Document, numbering more than 100, and
+     the Document's license notice requires Cover Texts, you must
+     enclose the copies in covers that carry, clearly and legibly, all
+     these Cover Texts: Front-Cover Texts on the front cover, and
      Back-Cover Texts on the back cover.  Both covers must also clearly
      and legibly identify you as the publisher of these copies.  The
@@ -2264 +3000 @@
      numbering more than 100, you must either include a
      machine-readable Transparent copy along with each Opaque copy, or
-     state in or with each Opaque copy a publicly-accessible
-     computer-network location containing a complete Transparent copy
-     of the Document, free of added material, which the general
-     network-using public has access to download anonymously at no
-     charge using public-standard network protocols.  If you use the
+     state in or with each Opaque copy a computer-network location from
+     which the general network-using public has access to download
+     using public-standard network protocols a complete Transparent
+     copy of the Document, free of added material.  If you use the
      latter option, you must take reasonably prudent steps, when you
      begin distribution of Opaque copies in quantity, to ensure that
@@ -2302 +3037 @@
           the Modified Version, together with at least five of the
           principal authors of the Document (all of its principal
-          authors, if it has less than five).
+          authors, if it has fewer than five), unless they release you
+          from this requirement.
 
        C. State on the Title page the name of the publisher of the
@@ -2323 +3059 @@
        H. Include an unaltered copy of this License.
 
-       I. Preserve the section entitled "History", and its title, and
-          add to it an item stating at least the title, year, new
+       I. Preserve the section Entitled "History", Preserve its Title,
+          and add to it an item stating at least the title, year, new
           authors, and publisher of the Modified Version as given on
-          the Title Page.  If there is no section entitled "History" in
+          the Title Page.  If there is no section Entitled "History" in
           the Document, create one stating the title, year, authors,
           and publisher of the Document as given on its Title Page,
@@ -2341 +3077 @@
           it refers to gives permission.
 
-       K. In any section entitled "Acknowledgments" or "Dedications",
-          preserve the section's title, and preserve in the section all
-          the substance and tone of each of the contributor
-          acknowledgments and/or dedications given therein.
+       K. For any section Entitled "Acknowledgements" or "Dedications",
+          Preserve the Title of the section, and preserve in the
+          section all the substance and tone of each of the contributor
+          acknowledgements and/or dedications given therein.
 
        L. Preserve all the Invariant Sections of the Document,
@@ -2351 +3087 @@
           titles.
 
-       M. Delete any section entitled "Endorsements".  Such a section
+       M. Delete any section Entitled "Endorsements".  Such a section
           may not be included in the Modified Version.
 
-       N. Do not retitle any existing section as "Endorsements" or to
-          conflict in title with any Invariant Section.
+       N. Do not retitle any existing section to be Entitled
+          "Endorsements" or to conflict in title with any Invariant
+          Section.
+
+       O. Preserve any Warranty Disclaimers.
 
      If the Modified Version includes new front-matter sections or
@@ -2365 +3104 @@
      other section titles.
 
-     You may add a section entitled "Endorsements", provided it contains
+     You may add a section Entitled "Endorsements", provided it contains
      nothing but endorsements of your Modified Version by various
      parties--for example, statements of peer review or that the text
@@ -2393 +3132 @@
      all of the Invariant Sections of all of the original documents,
      unmodified, and list them all as Invariant Sections of your
-     combined work in its license notice.
+     combined work in its license notice, and that you preserve all
+     their Warranty Disclaimers.
 
      The combined work need only contain one copy of this License, and
@@ -2405 +3145 @@
      combined work.
 
-     In the combination, you must combine any sections entitled
+     In the combination, you must combine any sections Entitled
      "History" in the various original documents, forming one section
-     entitled "History"; likewise combine any sections entitled
-     "Acknowledgments", and any sections entitled "Dedications".  You
-     must delete all sections entitled "Endorsements."
+     Entitled "History"; likewise combine any sections Entitled
+     "Acknowledgements", and any sections Entitled "Dedications".  You
+     must delete all sections Entitled "Endorsements."
 
   6. COLLECTIONS OF DOCUMENTS
@@ -2430 +3170 @@
      A compilation of the Document or its derivatives with other
      separate and independent documents or works, in or on a volume of
-     a storage or distribution medium, does not as a whole count as a
-     Modified Version of the Document, provided no compilation
-     copyright is claimed for the compilation.  Such a compilation is
-     called an "aggregate", and this License does not apply to the
-     other self-contained works thus compiled with the Document, on
-     account of their being thus compiled, if they are not themselves
-     derivative works of the Document.
+     a storage or distribution medium, is called an "aggregate" if the
+     copyright resulting from the compilation is not used to limit the
+     legal rights of the compilation's users beyond what the individual
+     works permit.  When the Document is included in an aggregate, this
+     License does not apply to the other works in the aggregate which
+     are not themselves derivative works of the Document.
 
      If the Cover Text requirement of section 3 is applicable to these
-     copies of the Document, then if the Document is less than one
-     quarter of the entire aggregate, the Document's Cover Texts may be
-     placed on covers that surround only the Document within the
-     aggregate.  Otherwise they must appear on covers around the whole
-     aggregate.
+     copies of the Document, then if the Document is less than one half
+     of the entire aggregate, the Document's Cover Texts may be placed
+     on covers that bracket the Document within the aggregate, or the
+     electronic equivalent of covers if the Document is in electronic
+     form.  Otherwise they must appear on printed covers that bracket
+     the whole aggregate.
 
   8. TRANSLATION
@@ -2453 +3193 @@
      translations of some or all Invariant Sections in addition to the
      original versions of these Invariant Sections.  You may include a
-     translation of this License provided that you also include the
-     original English version of this License.  In case of a
-     disagreement between the translation and the original English
-     version of this License, the original English version will prevail.
+     translation of this License, and all the license notices in the
+     Document, and any Warranty Disclaimers, provided that you also
+     include the original English version of this License and the
+     original versions of those notices and disclaimers.  In case of a
+     disagreement between the translation and the original version of
+     this License or a notice or disclaimer, the original version will
+     prevail.
+
+     If a section in the Document is Entitled "Acknowledgements",
+     "Dedications", or "History", the requirement (section 4) to
+     Preserve its Title (section 1) will typically require changing the
+     actual title.
 
   9. TERMINATION
@@ -2486 +3234 @@
      Free Software Foundation.
 
-ADDENDUM: How to use this License for your documents
-====================================================
+D.1 ADDENDUM: How to use this License for your documents
+========================================================
 
 To use this License in a document you have written, include a copy of
@@ -2495 +3243 @@
        Copyright (C)  YEAR  YOUR NAME.
        Permission is granted to copy, distribute and/or modify this document
-       under the terms of the GNU Free Documentation License, Version 1.1
+       under the terms of the GNU Free Documentation License, Version 1.2
        or any later version published by the Free Software Foundation;
-       with the Invariant Sections being LIST THEIR TITLES, with the
-       Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
-       A copy of the license is included in the section entitled ``GNU
+       with no Invariant Sections, no Front-Cover Texts, and no Back-Cover
+       Texts.  A copy of the license is included in the section entitled ``GNU
        Free Documentation License''.
 
-   If you have no Invariant Sections, write "with no Invariant Sections"
-instead of saying which ones are invariant.  If you have no Front-Cover
-Texts, write "no Front-Cover Texts" instead of "Front-Cover Texts being
-LIST"; likewise for Back-Cover Texts.
+   If you have Invariant Sections, Front-Cover Texts and Back-Cover
+Texts, replace the "with...Texts." line with this:
+
+         with the Invariant Sections being LIST THEIR TITLES, with
+         the Front-Cover Texts being LIST, and with the Back-Cover Texts
+         being LIST.
+
+   If you have Invariant Sections without Cover Texts, or some other
+combination of the three, merge those two alternatives to suit the
+situation.
 
    If your document contains nontrivial examples of program code, we
@@ -2518 +3271 @@
 *****************
 
+[index]
 * Menu:
 
-* # (comments), in commands:             Commands.
-* # (comments), in makefile:             Makefile Contents.
+* # (comments), in commands:             Command Syntax.      (line  27)
+* # (comments), in makefile:             Makefile Contents.   (line  41)
 * #include:                              Automatic Prerequisites.
-* $$@, support for:                      Automatic Variables.
-* $, in function call:                   Syntax of Functions.
-* $, in rules:                           Rule Syntax.
-* $, in variable name:                   Computed Names.
-* $, in variable reference:              Reference.
-* %, in pattern rules:                   Pattern Intro.
-* %, quoting in patsubst:                Text Functions.
-* %, quoting in static pattern:          Static Usage.
-* %, quoting in vpath:                   Selective Search.
-* %, quoting with \ (backslash) <1>:     Text Functions.
-* %, quoting with \ (backslash) <2>:     Static Usage.
-* %, quoting with \ (backslash):         Selective Search.
-* * (wildcard character):                Wildcards.
+                                                              (line  16)
+* $, in function call:                   Syntax of Functions. (line   6)
+* $, in rules:                           Rule Syntax.         (line  32)
+* $, in variable name:                   Computed Names.      (line   6)
+* $, in variable reference:              Reference.           (line   6)
+* %, in pattern rules:                   Pattern Intro.       (line   9)
+* %, quoting in patsubst:                Text Functions.      (line  26)
+* %, quoting in static pattern:          Static Usage.        (line  37)
+* %, quoting in vpath:                   Selective Search.    (line  38)
+* %, quoting with \ (backslash) <1>:     Text Functions.      (line  26)
+* %, quoting with \ (backslash) <2>:     Static Usage.        (line  37)
+* %, quoting with \ (backslash):         Selective Search.    (line  38)
+* * (wildcard character):                Wildcards.           (line   6)
 * +, and command execution:              Instead of Execution.
-* +, and commands:                       MAKE Variable.
-* +, and define:                         Sequences.
-* +=:                                    Appending.
-* +=, expansion:                         Reading Makefiles.
-* ,v (RCS file extension):               Catalogue of Rules.
-* - (in commands):                       Errors.
-* -, and define:                         Sequences.
-* --always-make:                         Options Summary.
-* --assume-new <1>:                      Options Summary.
+                                                              (line  58)
+* +, and commands:                       MAKE Variable.       (line  18)
+* +, and define:                         Sequences.           (line  50)
+* +=:                                    Appending.           (line   6)
+* +=, expansion:                         Reading Makefiles.   (line  33)
+* ,v (RCS file extension):               Catalogue of Rules.  (line 164)
+* - (in commands):                       Errors.              (line  19)
+* -, and define:                         Sequences.           (line  50)
+* --always-make:                         Options Summary.     (line  15)
+* --assume-new <1>:                      Options Summary.     (line 242)
 * --assume-new:                          Instead of Execution.
-* --assume-new, and recursion:           Options/Recursion.
-* --assume-old <1>:                      Options Summary.
+                                                              (line  33)
+* --assume-new, and recursion:           Options/Recursion.   (line  22)
+* --assume-old <1>:                      Options Summary.     (line 147)
 * --assume-old:                          Avoiding Compilation.
-* --assume-old, and recursion:           Options/Recursion.
-* --debug:                               Options Summary.
-* --directory <1>:                       Options Summary.
-* --directory:                           Recursion.
-* --directory, and --print-directory:    -w Option.
-* --directory, and recursion:            Options/Recursion.
-* --dry-run <1>:                         Options Summary.
+                                                              (line   6)
+* --assume-old, and recursion:           Options/Recursion.   (line  22)
+* --check-symlink-times:                 Options Summary.     (line 130)
+* --debug:                               Options Summary.     (line  42)
+* --directory <1>:                       Options Summary.     (line  26)
+* --directory:                           Recursion.           (line  20)
+* --directory, and --print-directory:    -w Option.           (line  20)
+* --directory, and recursion:            Options/Recursion.   (line  22)
+* --dry-run <1>:                         Options Summary.     (line 140)
 * --dry-run <2>:                         Instead of Execution.
-* --dry-run:                             Echoing.
-* --environment-overrides:               Options Summary.
-* --file <1>:                            Options Summary.
-* --file <2>:                            Makefile Arguments.
-* --file:                                Makefile Names.
-* --file, and recursion:                 Options/Recursion.
-* --help:                                Options Summary.
-* --ignore-errors <1>:                   Options Summary.
-* --ignore-errors:                       Errors.
-* --include-dir <1>:                     Options Summary.
-* --include-dir:                         Include.
-* --jobs <1>:                            Options Summary.
-* --jobs:                                Parallel.
-* --jobs, and recursion:                 Options/Recursion.
-* --just-print <1>:                      Options Summary.
+                                                              (line  14)
+* --dry-run:                             Echoing.             (line  18)
+* --environment-overrides:               Options Summary.     (line  78)
+* --file <1>:                            Options Summary.     (line  84)
+* --file <2>:                            Makefile Arguments.  (line   6)
+* --file:                                Makefile Names.      (line  23)
+* --file, and recursion:                 Options/Recursion.   (line  22)
+* --help:                                Options Summary.     (line  90)
+* --ignore-errors <1>:                   Options Summary.     (line  94)
+* --ignore-errors:                       Errors.              (line  30)
+* --include-dir <1>:                     Options Summary.     (line  99)
+* --include-dir:                         Include.             (line  52)
+* --jobs <1>:                            Options Summary.     (line 106)
+* --jobs:                                Parallel.            (line   6)
+* --jobs, and recursion:                 Options/Recursion.   (line  25)
+* --just-print <1>:                      Options Summary.     (line 139)
 * --just-print <2>:                      Instead of Execution.
-* --just-print:                          Echoing.
-* --keep-going <1>:                      Options Summary.
-* --keep-going <2>:                      Testing.
-* --keep-going:                          Errors.
-* --load-average <1>:                    Options Summary.
-* --load-average:                        Parallel.
-* --makefile <1>:                        Options Summary.
-* --makefile <2>:                        Makefile Arguments.
-* --makefile:                            Makefile Names.
-* --max-load <1>:                        Options Summary.
-* --max-load:                            Parallel.
-* --new-file <1>:                        Options Summary.
+                                                              (line  14)
+* --just-print:                          Echoing.             (line  18)
+* --keep-going <1>:                      Options Summary.     (line 115)
+* --keep-going <2>:                      Testing.             (line  16)
+* --keep-going:                          Errors.              (line  47)
+* --load-average <1>:                    Options Summary.     (line 122)
+* --load-average:                        Parallel.            (line  57)
+* --makefile <1>:                        Options Summary.     (line  85)
+* --makefile <2>:                        Makefile Arguments.  (line   6)
+* --makefile:                            Makefile Names.      (line  23)
+* --max-load <1>:                        Options Summary.     (line 123)
+* --max-load:                            Parallel.            (line  57)
+* --new-file <1>:                        Options Summary.     (line 241)
 * --new-file:                            Instead of Execution.
-* --new-file, and recursion:             Options/Recursion.
-* --no-builtin-rules:                    Options Summary.
-* --no-builtin-variables:                Options Summary.
-* --no-keep-going:                       Options Summary.
-* --no-print-directory <1>:              Options Summary.
-* --no-print-directory:                  -w Option.
-* --old-file <1>:                        Options Summary.
+                                                              (line  33)
+* --new-file, and recursion:             Options/Recursion.   (line  22)
+* --no-builtin-rules:                    Options Summary.     (line 175)
+* --no-builtin-variables:                Options Summary.     (line 188)
+* --no-keep-going:                       Options Summary.     (line 203)
+* --no-print-directory <1>:              Options Summary.     (line 233)
+* --no-print-directory:                  -w Option.           (line  20)
+* --old-file <1>:                        Options Summary.     (line 146)
 * --old-file:                            Avoiding Compilation.
-* --old-file, and recursion:             Options/Recursion.
-* --print-data-base:                     Options Summary.
-* --print-directory:                     Options Summary.
-* --print-directory, and --directory:    -w Option.
-* --print-directory, and recursion:      -w Option.
-* --print-directory, disabling:          -w Option.
-* --question <1>:                        Options Summary.
+                                                              (line   6)
+* --old-file, and recursion:             Options/Recursion.   (line  22)
+* --print-data-base:                     Options Summary.     (line 155)
+* --print-directory:                     Options Summary.     (line 225)
+* --print-directory, and --directory:    -w Option.           (line  20)
+* --print-directory, and recursion:      -w Option.           (line  20)
+* --print-directory, disabling:          -w Option.           (line  20)
+* --question <1>:                        Options Summary.     (line 167)
 * --question:                            Instead of Execution.
-* --quiet <1>:                           Options Summary.
-* --quiet:                               Echoing.
-* --recon <1>:                           Options Summary.
+                                                              (line  25)
+* --quiet <1>:                           Options Summary.     (line 198)
+* --quiet:                               Echoing.             (line  24)
+* --recon <1>:                           Options Summary.     (line 141)
 * --recon <2>:                           Instead of Execution.
-* --recon:                               Echoing.
-* --silent <1>:                          Options Summary.
-* --silent:                              Echoing.
-* --stop:                                Options Summary.
-* --touch <1>:                           Options Summary.
+                                                              (line  14)
+* --recon:                               Echoing.             (line  18)
+* --silent <1>:                          Options Summary.     (line 197)
+* --silent:                              Echoing.             (line  24)
+* --stop:                                Options Summary.     (line 204)
+* --touch <1>:                           Options Summary.     (line 212)
 * --touch:                               Instead of Execution.
-* --touch, and recursion:                MAKE Variable.
-* --version:                             Options Summary.
-* --warn-undefined-variables:            Options Summary.
-* --what-if <1>:                         Options Summary.
+                                                              (line  19)
+* --touch, and recursion:                MAKE Variable.       (line  34)
+* --version:                             Options Summary.     (line 220)
+* --warn-undefined-variables:            Options Summary.     (line 251)
+* --what-if <1>:                         Options Summary.     (line 240)
 * --what-if:                             Instead of Execution.
-* -B:                                    Options Summary.
-* -b:                                    Options Summary.
-* -C <1>:                                Options Summary.
-* -C:                                    Recursion.
-* -C, and -w:                            -w Option.
-* -C, and recursion:                     Options/Recursion.
-* -d:                                    Options Summary.
-* -e:                                    Options Summary.
+                                                              (line  33)
+* -B:                                    Options Summary.     (line  14)
+* -b:                                    Options Summary.     (line   9)
+* -C <1>:                                Options Summary.     (line  25)
+* -C:                                    Recursion.           (line  20)
+* -C, and -w:                            -w Option.           (line  20)
+* -C, and recursion:                     Options/Recursion.   (line  22)
+* -d:                                    Options Summary.     (line  33)
+* -e:                                    Options Summary.     (line  77)
 * -e (shell flag):                       Automatic Prerequisites.
-* -f <1>:                                Options Summary.
-* -f <2>:                                Makefile Arguments.
-* -f:                                    Makefile Names.
-* -f, and recursion:                     Options/Recursion.
-* -h:                                    Options Summary.
-* -I:                                    Options Summary.
-* -i <1>:                                Options Summary.
-* -i:                                    Errors.
-* -I:                                    Include.
-* -j <1>:                                Options Summary.
-* -j:                                    Parallel.
-* -j, and archive update:                Archive Pitfalls.
-* -j, and recursion:                     Options/Recursion.
-* -k <1>:                                Options Summary.
-* -k <2>:                                Testing.
-* -k:                                    Errors.
-* -l:                                    Options Summary.
-* -l (library search):                   Libraries/Search.
-* -l (load average):                     Parallel.
-* -m:                                    Options Summary.
+                                                              (line  66)
+* -f <1>:                                Options Summary.     (line  83)
+* -f <2>:                                Makefile Arguments.  (line   6)
+* -f:                                    Makefile Names.      (line  23)
+* -f, and recursion:                     Options/Recursion.   (line  22)
+* -h:                                    Options Summary.     (line  89)
+* -I:                                    Options Summary.     (line  98)
+* -i <1>:                                Options Summary.     (line  93)
+* -i:                                    Errors.              (line  30)
+* -I:                                    Include.             (line  52)
+* -j <1>:                                Options Summary.     (line 105)
+* -j:                                    Parallel.            (line   6)
+* -j, and archive update:                Archive Pitfalls.    (line   6)
+* -j, and recursion:                     Options/Recursion.   (line  25)
+* -k <1>:                                Options Summary.     (line 114)
+* -k <2>:                                Testing.             (line  16)
+* -k:                                    Errors.              (line  47)
+* -L:                                    Options Summary.     (line 129)
+* -l:                                    Options Summary.     (line 121)
+* -l (library search):                   Libraries/Search.    (line   6)
+* -l (load average):                     Parallel.            (line  57)
+* -m:                                    Options Summary.     (line  10)
 * -M (to compiler):                      Automatic Prerequisites.
+                                                              (line  18)
 * -MM (to GNU compiler):                 Automatic Prerequisites.
-* -n <1>:                                Options Summary.
+                                                              (line  68)
+* -n <1>:                                Options Summary.     (line 138)
 * -n <2>:                                Instead of Execution.
-* -n:                                    Echoing.
-* -o <1>:                                Options Summary.
+                                                              (line  14)
+* -n:                                    Echoing.             (line  18)
+* -o <1>:                                Options Summary.     (line 145)
 * -o:                                    Avoiding Compilation.
-* -o, and recursion:                     Options/Recursion.
-* -p:                                    Options Summary.
-* -q <1>:                                Options Summary.
+                                                              (line   6)
+* -o, and recursion:                     Options/Recursion.   (line  22)
+* -p:                                    Options Summary.     (line 154)
+* -q <1>:                                Options Summary.     (line 166)
 * -q:                                    Instead of Execution.
-* -R:                                    Options Summary.
-* -r:                                    Options Summary.
-* -S:                                    Options Summary.
-* -s <1>:                                Options Summary.
-* -s:                                    Echoing.
-* -t <1>:                                Options Summary.
+                                                              (line  25)
+* -R:                                    Options Summary.     (line 187)
+* -r:                                    Options Summary.     (line 174)
+* -S:                                    Options Summary.     (line 202)
+* -s <1>:                                Options Summary.     (line 196)
+* -s:                                    Echoing.             (line  24)
+* -t <1>:                                Options Summary.     (line 211)
 * -t:                                    Instead of Execution.
-* -t, and recursion:                     MAKE Variable.
-* -v:                                    Options Summary.
-* -W:                                    Options Summary.
-* -w:                                    Options Summary.
+                                                              (line  19)
+* -t, and recursion:                     MAKE Variable.       (line  34)
+* -v:                                    Options Summary.     (line 219)
+* -W:                                    Options Summary.     (line 239)
+* -w:                                    Options Summary.     (line 224)
 * -W:                                    Instead of Execution.
-* -w, and -C:                            -w Option.
-* -w, and recursion:                     -w Option.
-* -W, and recursion:                     Options/Recursion.
-* -w, disabling:                         -w Option.
+                                                              (line  33)
+* -w, and -C:                            -w Option.           (line  20)
+* -w, and recursion:                     -w Option.           (line  20)
+* -W, and recursion:                     Options/Recursion.   (line  22)
+* -w, disabling:                         -w Option.           (line  20)
 * .a (archives):                         Archive Suffix Rules.
-* .C:                                    Catalogue of Rules.
-* .c:                                    Catalogue of Rules.
-* .cc:                                   Catalogue of Rules.
-* .ch:                                   Catalogue of Rules.
+                                                              (line   6)
+* .C:                                    Catalogue of Rules.  (line  39)
+* .c:                                    Catalogue of Rules.  (line  35)
+* .cc:                                   Catalogue of Rules.  (line  39)
+* .ch:                                   Catalogue of Rules.  (line 151)
+* .cpp:                                  Catalogue of Rules.  (line  39)
 * .d:                                    Automatic Prerequisites.
-* .def:                                  Catalogue of Rules.
-* .dvi:                                  Catalogue of Rules.
-* .F:                                    Catalogue of Rules.
-* .f:                                    Catalogue of Rules.
-* .info:                                 Catalogue of Rules.
-* .l:                                    Catalogue of Rules.
-* .LIBPATTERNS, and link libraries:      Libraries/Search.
-* .ln:                                   Catalogue of Rules.
-* .mod:                                  Catalogue of Rules.
-* .o:                                    Catalogue of Rules.
-* .p:                                    Catalogue of Rules.
-* .PRECIOUS intermediate files:          Chained Rules.
-* .r:                                    Catalogue of Rules.
-* .S:                                    Catalogue of Rules.
-* .s:                                    Catalogue of Rules.
-* .sh:                                   Catalogue of Rules.
-* .sym:                                  Catalogue of Rules.
-* .tex:                                  Catalogue of Rules.
-* .texi:                                 Catalogue of Rules.
-* .texinfo:                              Catalogue of Rules.
-* .txinfo:                               Catalogue of Rules.
-* .w:                                    Catalogue of Rules.
-* .web:                                  Catalogue of Rules.
-* .y:                                    Catalogue of Rules.
-* :: rules (double-colon):               Double-Colon.
-* := <1>:                                Setting.
-* :=:                                    Flavors.
-* = <1>:                                 Setting.
-* =:                                     Flavors.
-* =, expansion:                          Reading Makefiles.
-* ? (wildcard character):                Wildcards.
-* ?= <1>:                                Setting.
-* ?=:                                    Flavors.
-* ?=, expansion:                         Reading Makefiles.
-* @ (in commands):                       Echoing.
-* @, and define:                         Sequences.
-* [...] (wildcard characters):           Wildcards.
-* \ (backslash), for continuation lines: Simple Makefile.
-* \ (backslash), in commands:            Execution.
-* \ (backslash), to quote % <1>:         Text Functions.
-* \ (backslash), to quote % <2>:         Static Usage.
-* \ (backslash), to quote %:             Selective Search.
-* __.SYMDEF:                             Archive Symbols.
-* algorithm for directory search:        Search Algorithm.
-* all (standard target):                 Goals.
-* appending to variables:                Appending.
-* ar:                                    Implicit Variables.
-* archive:                               Archives.
-* archive member targets:                Archive Members.
-* archive symbol directory updating:     Archive Symbols.
-* archive, and -j:                       Archive Pitfalls.
-* archive, and parallel execution:       Archive Pitfalls.
+                                                              (line  81)
+* .def:                                  Catalogue of Rules.  (line  74)
+* .dvi:                                  Catalogue of Rules.  (line 151)
+* .F:                                    Catalogue of Rules.  (line  49)
+* .f:                                    Catalogue of Rules.  (line  49)
+* .info:                                 Catalogue of Rules.  (line 158)
+* .l:                                    Catalogue of Rules.  (line 124)
+* .LIBPATTERNS, and link libraries:      Libraries/Search.    (line   6)
+* .ln:                                   Catalogue of Rules.  (line 146)
+* .mod:                                  Catalogue of Rules.  (line  74)
+* .o:                                    Catalogue of Rules.  (line  35)
+* .p:                                    Catalogue of Rules.  (line  45)
+* .PRECIOUS intermediate files:          Chained Rules.       (line  56)
+* .r:                                    Catalogue of Rules.  (line  49)
+* .S:                                    Catalogue of Rules.  (line  82)
+* .s:                                    Catalogue of Rules.  (line  79)
+* .sh:                                   Catalogue of Rules.  (line 180)
+* .sym:                                  Catalogue of Rules.  (line  74)
+* .tex:                                  Catalogue of Rules.  (line 151)
+* .texi:                                 Catalogue of Rules.  (line 158)
+* .texinfo:                              Catalogue of Rules.  (line 158)
+* .txinfo:                               Catalogue of Rules.  (line 158)
+* .w:                                    Catalogue of Rules.  (line 151)
+* .web:                                  Catalogue of Rules.  (line 151)
+* .y:                                    Catalogue of Rules.  (line 120)
+* :: rules (double-colon):               Double-Colon.        (line   6)
+* := <1>:                                Setting.             (line   6)
+* :=:                                    Flavors.             (line  56)
+* = <1>:                                 Setting.             (line   6)
+* =:                                     Flavors.             (line  10)
+* =, expansion:                          Reading Makefiles.   (line  33)
+* ? (wildcard character):                Wildcards.           (line   6)
+* ?= <1>:                                Setting.             (line   6)
+* ?=:                                    Flavors.             (line 129)
+* ?=, expansion:                         Reading Makefiles.   (line  33)
+* @ (in commands):                       Echoing.             (line   6)
+* @, and define:                         Sequences.           (line  50)
+* [...] (wildcard characters):           Wildcards.           (line   6)
+* \ (backslash), for continuation lines: Simple Makefile.     (line  40)
+* \ (backslash), in commands:            Splitting Lines.     (line   6)
+* \ (backslash), to quote % <1>:         Text Functions.      (line  26)
+* \ (backslash), to quote % <2>:         Static Usage.        (line  37)
+* \ (backslash), to quote %:             Selective Search.    (line  38)
+* __.SYMDEF:                             Archive Symbols.     (line   6)
+* abspath:                               File Name Functions. (line 121)
+* algorithm for directory search:        Search Algorithm.    (line   6)
+* all (standard target):                 Goals.               (line  72)
+* appending to variables:                Appending.           (line   6)
+* ar:                                    Implicit Variables.  (line  41)
+* archive:                               Archives.            (line   6)
+* archive member targets:                Archive Members.     (line   6)
+* archive symbol directory updating:     Archive Symbols.     (line   6)
+* archive, and -j:                       Archive Pitfalls.    (line   6)
+* archive, and parallel execution:       Archive Pitfalls.    (line   6)
 * archive, suffix rule for:              Archive Suffix Rules.
-* Arg list too long:                     Options/Recursion.
-* arguments of functions:                Syntax of Functions.
-* as <1>:                                Implicit Variables.
-* as:                                    Catalogue of Rules.
-* assembly, rule to compile:             Catalogue of Rules.
+                                                              (line   6)
+* Arg list too long:                     Options/Recursion.   (line  57)
+* arguments of functions:                Syntax of Functions. (line   6)
+* as <1>:                                Implicit Variables.  (line  44)
+* as:                                    Catalogue of Rules.  (line  79)
+* assembly, rule to compile:             Catalogue of Rules.  (line  79)
 * automatic generation of prerequisites <1>: Automatic Prerequisites.
-* automatic generation of prerequisites: Include.
-* automatic variables:                   Automatic Variables.
-* automatic variables in prerequisites:  Automatic Variables.
-* backquotes:                            Shell Function.
-* backslash (\), for continuation lines: Simple Makefile.
-* backslash (\), in commands:            Execution.
-* backslash (\), to quote % <1>:         Text Functions.
-* backslash (\), to quote % <2>:         Static Usage.
-* backslash (\), to quote %:             Selective Search.
+                                                              (line   6)
+* automatic generation of prerequisites: Include.             (line  50)
+* automatic variables:                   Automatic Variables. (line   6)
+* automatic variables in prerequisites:  Automatic Variables. (line  17)
+* backquotes:                            Shell Function.      (line   6)
+* backslash (\), for continuation lines: Simple Makefile.     (line  40)
+* backslash (\), in commands:            Splitting Lines.     (line   6)
+* backslash (\), to quote % <1>:         Text Functions.      (line  26)
+* backslash (\), to quote % <2>:         Static Usage.        (line  37)
+* backslash (\), to quote %:             Selective Search.    (line  38)
 * backslashes in pathnames and wildcard expansion: Wildcard Pitfall.
-* basename:                              File Name Functions.
+                                                              (line  31)
+* basename:                              File Name Functions. (line  57)
 * binary packages:                       Install Command Categories.
-* broken pipe:                           Parallel.
-* bugs, reporting:                       Bugs.
-* built-in special targets:              Special Targets.
-* C++, rule to compile:                  Catalogue of Rules.
-* C, rule to compile:                    Catalogue of Rules.
-* cc <1>:                                Implicit Variables.
-* cc:                                    Catalogue of Rules.
-* cd (shell command) <1>:                MAKE Variable.
-* cd (shell command):                    Execution.
-* chains of rules:                       Chained Rules.
-* check (standard target):               Goals.
-* clean (standard target):               Goals.
-* clean target <1>:                      Cleanup.
-* clean target:                          Simple Makefile.
-* cleaning up:                           Cleanup.
-* clobber (standard target):             Goals.
-* co <1>:                                Implicit Variables.
-* co:                                    Catalogue of Rules.
+                                                              (line  80)
+* broken pipe:                           Parallel.            (line  30)
+* bugs, reporting:                       Bugs.                (line   6)
+* built-in special targets:              Special Targets.     (line   6)
+* C++, rule to compile:                  Catalogue of Rules.  (line  39)
+* C, rule to compile:                    Catalogue of Rules.  (line  35)
+* cc <1>:                                Implicit Variables.  (line  47)
+* cc:                                    Catalogue of Rules.  (line  35)
+* cd (shell command) <1>:                MAKE Variable.       (line  16)
+* cd (shell command):                    Execution.           (line  10)
+* chains of rules:                       Chained Rules.       (line   6)
+* check (standard target):               Goals.               (line 114)
+* clean (standard target):               Goals.               (line  75)
+* clean target <1>:                      Cleanup.             (line  11)
+* clean target:                          Simple Makefile.     (line  83)
+* cleaning up:                           Cleanup.             (line   6)
+* clobber (standard target):             Goals.               (line  86)
+* co <1>:                                Implicit Variables.  (line  56)
+* co:                                    Catalogue of Rules.  (line 164)
 * combining rules by prerequisite:       Combine By Prerequisite.
+                                                              (line   6)
 * command line variable definitions, and recursion: Options/Recursion.
-* command line variables:                Overriding.
-* commands:                              Rule Syntax.
-* commands, backslash (\) in:            Execution.
-* commands, comments in:                 Commands.
-* commands, echoing:                     Echoing.
-* commands, empty:                       Empty Commands.
-* commands, errors in:                   Errors.
-* commands, execution:                   Execution.
-* commands, execution in parallel:       Parallel.
-* commands, expansion:                   Shell Function.
-* commands, how to write:                Commands.
+                                                              (line  17)
+* command line variables:                Overriding.          (line   6)
+* command syntax:                        Command Syntax.      (line   6)
+* commands:                              Rule Syntax.         (line  26)
+* commands setting shell variables:      Execution.           (line  10)
+* commands, backslash (\) in:            Splitting Lines.     (line   6)
+* commands, comments in:                 Command Syntax.      (line  27)
+* commands, echoing:                     Echoing.             (line   6)
+* commands, empty:                       Empty Commands.      (line   6)
+* commands, errors in:                   Errors.              (line   6)
+* commands, execution:                   Execution.           (line   6)
+* commands, execution in parallel:       Parallel.            (line   6)
+* commands, expansion:                   Shell Function.      (line   6)
+* commands, how to write:                Commands.            (line   6)
 * commands, instead of executing:        Instead of Execution.
-* commands, introduction to:             Rule Introduction.
-* commands, quoting newlines in:         Execution.
-* commands, sequences of:                Sequences.
-* comments, in commands:                 Commands.
-* comments, in makefile:                 Makefile Contents.
-* compatibility:                         Features.
-* compatibility in exporting:            Variables/Recursion.
-* compilation, testing:                  Testing.
-* computed variable name:                Computed Names.
-* conditional expansion:                 If Function.
-* conditional variable assignment:       Flavors.
-* conditionals:                          Conditionals.
-* continuation lines:                    Simple Makefile.
+                                                              (line   6)
+* commands, introduction to:             Rule Introduction.   (line   8)
+* commands, quoting newlines in:         Splitting Lines.     (line   6)
+* commands, sequences of:                Sequences.           (line   6)
+* commands, splitting:                   Splitting Lines.     (line   6)
+* commands, using variables in:          Variables in Commands.
+                                                              (line   6)
+* comments, in commands:                 Command Syntax.      (line  27)
+* comments, in makefile:                 Makefile Contents.   (line  41)
+* compatibility:                         Features.            (line   6)
+* compatibility in exporting:            Variables/Recursion. (line 105)
+* compilation, testing:                  Testing.             (line   6)
+* computed variable name:                Computed Names.      (line   6)
+* conditional expansion:                 Conditional Functions.
+                                                              (line   6)
+* conditional variable assignment:       Flavors.             (line 129)
+* conditionals:                          Conditionals.        (line   6)
+* continuation lines:                    Simple Makefile.     (line  40)
 * controlling make:                      Make Control Functions.
+                                                              (line   6)
 * conventions for makefiles:             Makefile Conventions.
-* ctangle <1>:                           Implicit Variables.
-* ctangle:                               Catalogue of Rules.
-* cweave <1>:                            Implicit Variables.
-* cweave:                                Catalogue of Rules.
-* data base of make rules:               Options Summary.
-* deducing commands (implicit rules):    make Deduces.
-* default directories for included makefiles: Include.
-* default goal <1>:                      Rules.
-* default goal:                          How Make Works.
-* default makefile name:                 Makefile Names.
-* default rules, last-resort:            Last Resort.
-* define, expansion:                     Reading Makefiles.
-* defining variables verbatim:           Defining.
-* deletion of target files <1>:          Interrupts.
-* deletion of target files:              Errors.
-* directive:                             Makefile Contents.
-* directories, printing them:            -w Option.
-* directories, updating archive symbol:  Archive Symbols.
-* directory part:                        File Name Functions.
-* directory search (VPATH):              Directory Search.
+                                                              (line   6)
+* ctangle <1>:                           Implicit Variables.  (line 107)
+* ctangle:                               Catalogue of Rules.  (line 151)
+* cweave <1>:                            Implicit Variables.  (line 101)
+* cweave:                                Catalogue of Rules.  (line 151)
+* data base of make rules:               Options Summary.     (line 155)
+* deducing commands (implicit rules):    make Deduces.        (line   6)
+* default directories for included makefiles: Include.        (line  52)
+* default goal <1>:                      Rules.               (line  11)
+* default goal:                          How Make Works.      (line  11)
+* default makefile name:                 Makefile Names.      (line   6)
+* default rules, last-resort:            Last Resort.         (line   6)
+* define, expansion:                     Reading Makefiles.   (line  33)
+* defining variables verbatim:           Defining.            (line   6)
+* deletion of target files <1>:          Interrupts.          (line   6)
+* deletion of target files:              Errors.              (line  64)
+* directive:                             Makefile Contents.   (line  28)
+* directories, printing them:            -w Option.           (line   6)
+* directories, updating archive symbol:  Archive Symbols.     (line   6)
+* directory part:                        File Name Functions. (line  17)
+* directory search (VPATH):              Directory Search.    (line   6)
 * directory search (VPATH), and implicit rules: Implicit/Search.
+                                                              (line   6)
 * directory search (VPATH), and link libraries: Libraries/Search.
+                                                              (line   6)
 * directory search (VPATH), and shell commands: Commands/Search.
-* directory search algorithm:            Search Algorithm.
-* directory search, traditional (GPATH): Search Algorithm.
-* dist (standard target):                Goals.
-* distclean (standard target):           Goals.
-* dollar sign ($), in function call:     Syntax of Functions.
-* dollar sign ($), in rules:             Rule Syntax.
-* dollar sign ($), in variable name:     Computed Names.
-* dollar sign ($), in variable reference: Reference.
-* double-colon rules:                    Double-Colon.
-* duplicate words, removing:             Text Functions.
-* E2BIG:                                 Options/Recursion.
-* echoing of commands:                   Echoing.
-* editor:                                Introduction.
-* Emacs (M-x compile):                   Errors.
-* empty commands:                        Empty Commands.
-* empty targets:                         Empty Targets.
-* environment:                           Environment.
-* environment, and recursion:            Variables/Recursion.
-* environment, SHELL in:                 Execution.
+                                                              (line   6)
+* directory search algorithm:            Search Algorithm.    (line   6)
+* directory search, traditional (GPATH): Search Algorithm.    (line  42)
+* dist (standard target):                Goals.               (line 106)
+* distclean (standard target):           Goals.               (line  84)
+* dollar sign ($), in function call:     Syntax of Functions. (line   6)
+* dollar sign ($), in rules:             Rule Syntax.         (line  32)
+* dollar sign ($), in variable name:     Computed Names.      (line   6)
+* dollar sign ($), in variable reference: Reference.          (line   6)
+* DOS, choosing a shell in:              Choosing the Shell.  (line  36)
+* double-colon rules:                    Double-Colon.        (line   6)
+* duplicate words, removing:             Text Functions.      (line 155)
+* E2BIG:                                 Options/Recursion.   (line  57)
+* echoing of commands:                   Echoing.             (line   6)
+* editor:                                Introduction.        (line  22)
+* Emacs (M-x compile):                   Errors.              (line  62)
+* empty commands:                        Empty Commands.      (line   6)
+* empty targets:                         Empty Targets.       (line   6)
+* environment:                           Environment.         (line   6)
+* environment, and recursion:            Variables/Recursion. (line   6)
+* environment, SHELL in:                 Choosing the Shell.  (line  10)
 * error, stopping on:                    Make Control Functions.
-* errors (in commands):                  Errors.
-* errors with wildcards:                 Wildcard Pitfall.
-* evaluating makefile syntax:            Eval Function.
-* execution, in parallel:                Parallel.
+                                                              (line  11)
+* errors (in commands):                  Errors.              (line   6)
+* errors with wildcards:                 Wildcard Pitfall.    (line   6)
+* evaluating makefile syntax:            Eval Function.       (line   6)
+* execution, in parallel:                Parallel.            (line   6)
 * execution, instead of:                 Instead of Execution.
-* execution, of commands:                Execution.
-* exit status (errors):                  Errors.
-* explicit rule, definition of:          Makefile Contents.
-* explicit rule, expansion:              Reading Makefiles.
-* exporting variables:                   Variables/Recursion.
-* f77 <1>:                               Implicit Variables.
-* f77:                                   Catalogue of Rules.
+                                                              (line   6)
+* execution, of commands:                Execution.           (line   6)
+* exit status (errors):                  Errors.              (line   6)
+* exit status of make:                   Running.             (line  18)
+* expansion, secondary:                  Secondary Expansion. (line   6)
+* explicit rule, definition of:          Makefile Contents.   (line  10)
+* explicit rule, expansion:              Reading Makefiles.   (line  62)
+* explicit rules, secondary expansion of: Secondary Expansion.
+                                                              (line 106)
+* exporting variables:                   Variables/Recursion. (line   6)
+* f77 <1>:                               Implicit Variables.  (line  64)
+* f77:                                   Catalogue of Rules.  (line  49)
 * FDL, GNU Free Documentation License:   GNU Free Documentation License.
-* features of GNU make:                  Features.
-* features, missing:                     Missing.
-* file name functions:                   File Name Functions.
-* file name of makefile:                 Makefile Names.
-* file name of makefile, how to specify: Makefile Names.
-* file name prefix, adding:              File Name Functions.
-* file name suffix:                      File Name Functions.
-* file name suffix, adding:              File Name Functions.
-* file name with wildcards:              Wildcards.
-* file name, basename of:                File Name Functions.
-* file name, directory part:             File Name Functions.
-* file name, nondirectory part:          File Name Functions.
+                                                              (line   6)
+* features of GNU make:                  Features.            (line   6)
+* features, missing:                     Missing.             (line   6)
+* file name functions:                   File Name Functions. (line   6)
+* file name of makefile:                 Makefile Names.      (line   6)
+* file name of makefile, how to specify: Makefile Names.      (line  30)
+* file name prefix, adding:              File Name Functions. (line  79)
+* file name suffix:                      File Name Functions. (line  43)
+* file name suffix, adding:              File Name Functions. (line  68)
+* file name with wildcards:              Wildcards.           (line   6)
+* file name, abspath of:                 File Name Functions. (line 121)
+* file name, basename of:                File Name Functions. (line  57)
+* file name, directory part:             File Name Functions. (line  17)
+* file name, nondirectory part:          File Name Functions. (line  27)
+* file name, realpath of:                File Name Functions. (line 114)
 * files, assuming new:                   Instead of Execution.
+                                                              (line  33)
 * files, assuming old:                   Avoiding Compilation.
+                                                              (line   6)
 * files, avoiding recompilation of:      Avoiding Compilation.
-* files, intermediate:                   Chained Rules.
-* filtering out words:                   Text Functions.
-* filtering words:                       Text Functions.
-* finding strings:                       Text Functions.
-* flags:                                 Options Summary.
-* flags for compilers:                   Implicit Variables.
-* flavors of variables:                  Flavors.
-* FORCE:                                 Force Targets.
-* force targets:                         Force Targets.
-* Fortran, rule to compile:              Catalogue of Rules.
-* functions:                             Functions.
+                                                              (line   6)
+* files, intermediate:                   Chained Rules.       (line  16)
+* filtering out words:                   Text Functions.      (line 132)
+* filtering words:                       Text Functions.      (line 114)
+* finding strings:                       Text Functions.      (line 103)
+* flags:                                 Options Summary.     (line   6)
+* flags for compilers:                   Implicit Variables.  (line   6)
+* flavor of variable:                    Flavor Function.     (line   6)
+* flavors of variables:                  Flavors.             (line   6)
+* FORCE:                                 Force Targets.       (line   6)
+* force targets:                         Force Targets.       (line   6)
+* Fortran, rule to compile:              Catalogue of Rules.  (line  49)
+* functions:                             Functions.           (line   6)
 * functions, for controlling make:       Make Control Functions.
-* functions, for file names:             File Name Functions.
-* functions, for text:                   Text Functions.
-* functions, syntax of:                  Syntax of Functions.
-* functions, user defined:               Call Function.
-* g++ <1>:                               Implicit Variables.
-* g++:                                   Catalogue of Rules.
-* gcc:                                   Catalogue of Rules.
+                                                              (line   6)
+* functions, for file names:             File Name Functions. (line   6)
+* functions, for text:                   Text Functions.      (line   6)
+* functions, syntax of:                  Syntax of Functions. (line   6)
+* functions, user defined:               Call Function.       (line   6)
+* g++ <1>:                               Implicit Variables.  (line  53)
+* g++:                                   Catalogue of Rules.  (line  39)
+* gcc:                                   Catalogue of Rules.  (line  35)
 * generating prerequisites automatically <1>: Automatic Prerequisites.
-* generating prerequisites automatically: Include.
-* get <1>:                               Implicit Variables.
-* get:                                   Catalogue of Rules.
-* globbing (wildcards):                  Wildcards.
-* goal:                                  How Make Works.
-* goal, default <1>:                     Rules.
-* goal, default:                         How Make Works.
-* goal, how to specify:                  Goals.
-* home directory:                        Wildcards.
-* IEEE Standard 1003.2:                  Overview.
-* ifdef, expansion:                      Reading Makefiles.
-* ifeq, expansion:                       Reading Makefiles.
-* ifndef, expansion:                     Reading Makefiles.
-* ifneq, expansion:                      Reading Makefiles.
-* implicit rule:                         Implicit Rules.
-* implicit rule, and directory search:   Implicit/Search.
-* implicit rule, and VPATH:              Implicit/Search.
-* implicit rule, definition of:          Makefile Contents.
-* implicit rule, expansion:              Reading Makefiles.
-* implicit rule, how to use:             Using Implicit.
-* implicit rule, introduction to:        make Deduces.
-* implicit rule, predefined:             Catalogue of Rules.
+                                                              (line   6)
+* generating prerequisites automatically: Include.            (line  50)
+* get <1>:                               Implicit Variables.  (line  67)
+* get:                                   Catalogue of Rules.  (line 173)
+* globbing (wildcards):                  Wildcards.           (line   6)
+* goal:                                  How Make Works.      (line  11)
+* goal, default <1>:                     Rules.               (line  11)
+* goal, default:                         How Make Works.      (line  11)
+* goal, how to specify:                  Goals.               (line   6)
+* home directory:                        Wildcards.           (line  11)
+* IEEE Standard 1003.2:                  Overview.            (line  13)
+* ifdef, expansion:                      Reading Makefiles.   (line  51)
+* ifeq, expansion:                       Reading Makefiles.   (line  51)
+* ifndef, expansion:                     Reading Makefiles.   (line  51)
+* ifneq, expansion:                      Reading Makefiles.   (line  51)
+* implicit rule:                         Implicit Rules.      (line   6)
+* implicit rule, and directory search:   Implicit/Search.     (line   6)
+* implicit rule, and VPATH:              Implicit/Search.     (line   6)
+* implicit rule, definition of:          Makefile Contents.   (line  16)
+* implicit rule, expansion:              Reading Makefiles.   (line  62)
+* implicit rule, how to use:             Using Implicit.      (line   6)
+* implicit rule, introduction to:        make Deduces.        (line   6)
+* implicit rule, predefined:             Catalogue of Rules.  (line   6)
 * implicit rule, search algorithm:       Implicit Rule Search.
-* included makefiles, default directories: Include.
+                                                              (line   6)
+* implicit rules, secondary expansion of: Secondary Expansion.
+                                                              (line 146)
+* included makefiles, default directories: Include.           (line  52)
 * including (MAKEFILE_LIST variable):    MAKEFILE_LIST Variable.
-* including (MAKEFILES variable):        MAKEFILES Variable.
-* including other makefiles:             Include.
-* incompatibilities:                     Missing.
-* Info, rule to format:                  Catalogue of Rules.
-* install (standard target):             Goals.
-* intermediate files:                    Chained Rules.
-* intermediate files, preserving:        Chained Rules.
-* intermediate targets, explicit:        Special Targets.
-* interrupt:                             Interrupts.
-* job slots:                             Parallel.
-* job slots, and recursion:              Options/Recursion.
-* jobs, limiting based on load:          Parallel.
-* joining lists of words:                File Name Functions.
-* killing (interruption):                Interrupts.
-* last-resort default rules:             Last Resort.
-* ld:                                    Catalogue of Rules.
-* lex <1>:                               Implicit Variables.
-* lex:                                   Catalogue of Rules.
-* Lex, rule to run:                      Catalogue of Rules.
-* libraries for linking, directory search: Libraries/Search.
+                                                              (line   6)
+* including (MAKEFILES variable):        MAKEFILES Variable.  (line   6)
+* including other makefiles:             Include.             (line   6)
+* incompatibilities:                     Missing.             (line   6)
+* Info, rule to format:                  Catalogue of Rules.  (line 158)
+* install (standard target):             Goals.               (line  92)
+* intermediate files:                    Chained Rules.       (line  16)
+* intermediate files, preserving:        Chained Rules.       (line  46)
+* intermediate targets, explicit:        Special Targets.     (line  44)
+* interrupt:                             Interrupts.          (line   6)
+* job slots:                             Parallel.            (line   6)
+* job slots, and recursion:              Options/Recursion.   (line  25)
+* jobs, limiting based on load:          Parallel.            (line  57)
+* joining lists of words:                File Name Functions. (line  90)
+* killing (interruption):                Interrupts.          (line   6)
+* last-resort default rules:             Last Resort.         (line   6)
+* ld:                                    Catalogue of Rules.  (line  86)
+* lex <1>:                               Implicit Variables.  (line  71)
+* lex:                                   Catalogue of Rules.  (line 124)
+* Lex, rule to run:                      Catalogue of Rules.  (line 124)
+* libraries for linking, directory search: Libraries/Search.  (line   6)
 * library archive, suffix rule for:      Archive Suffix Rules.
-* limiting jobs based on load:           Parallel.
-* link libraries, and directory search:  Libraries/Search.
-* link libraries, patterns matching:     Libraries/Search.
-* linking, predefined rule for:          Catalogue of Rules.
-* lint:                                  Catalogue of Rules.
-* lint, rule to run:                     Catalogue of Rules.
-* list of all prerequisites:             Automatic Variables.
-* list of changed prerequisites:         Automatic Variables.
-* load average:                          Parallel.
-* loops in variable expansion:           Flavors.
-* lpr (shell command) <1>:               Empty Targets.
-* lpr (shell command):                   Wildcard Examples.
-* m2c:                                   Catalogue of Rules.
-* macro:                                 Using Variables.
+                                                              (line   6)
+* limiting jobs based on load:           Parallel.            (line  57)
+* link libraries, and directory search:  Libraries/Search.    (line   6)
+* link libraries, patterns matching:     Libraries/Search.    (line   6)
+* linking, predefined rule for:          Catalogue of Rules.  (line  86)
+* lint <1>:                              Implicit Variables.  (line  78)
+* lint:                                  Catalogue of Rules.  (line 146)
+* lint, rule to run:                     Catalogue of Rules.  (line 146)
+* list of all prerequisites:             Automatic Variables. (line  61)
+* list of changed prerequisites:         Automatic Variables. (line  51)
+* load average:                          Parallel.            (line  57)
+* loops in variable expansion:           Flavors.             (line  44)
+* lpr (shell command) <1>:               Empty Targets.       (line  25)
+* lpr (shell command):                   Wildcard Examples.   (line  21)
+* m2c <1>:                               Implicit Variables.  (line  81)
+* m2c:                                   Catalogue of Rules.  (line  74)
+* macro:                                 Using Variables.     (line  10)
 * make depend:                           Automatic Prerequisites.
-* MAKECMDGOALS:                          Goals.
-* makefile:                              Introduction.
-* makefile name:                         Makefile Names.
-* makefile name, how to specify:         Makefile Names.
-* makefile rule parts:                   Rule Introduction.
-* makefile syntax, evaluating:           Eval Function.
-* makefile, and MAKEFILES variable:      MAKEFILES Variable.
+                                                              (line  37)
+* makefile:                              Introduction.        (line   7)
+* makefile name:                         Makefile Names.      (line   6)
+* makefile name, how to specify:         Makefile Names.      (line  30)
+* makefile rule parts:                   Rule Introduction.   (line   6)
+* makefile syntax, evaluating:           Eval Function.       (line   6)
+* makefile, and MAKEFILES variable:      MAKEFILES Variable.  (line   6)
 * makefile, conventions for:             Makefile Conventions.
-* makefile, how make processes:          How Make Works.
-* makefile, how to write:                Makefiles.
-* makefile, including:                   Include.
+                                                              (line   6)
+* makefile, how make processes:          How Make Works.      (line   6)
+* makefile, how to write:                Makefiles.           (line   6)
+* makefile, including:                   Include.             (line   6)
 * makefile, overriding:                  Overriding Makefiles.
-* makefile, parsing:                     Reading Makefiles.
-* makefile, remaking of:                 Remaking Makefiles.
-* makefile, simple:                      Simple Makefile.
+                                                              (line   6)
+* makefile, parsing:                     Reading Makefiles.   (line   6)
+* makefile, remaking of:                 Remaking Makefiles.  (line   6)
+* makefile, simple:                      Simple Makefile.     (line   6)
 * makefiles, and MAKEFILE_LIST variable: MAKEFILE_LIST Variable.
-* makefiles, and special variables:      Special Variables.
-* makeinfo <1>:                          Implicit Variables.
-* makeinfo:                              Catalogue of Rules.
+                                                              (line   6)
+* makefiles, and special variables:      Special Variables.   (line   6)
+* makeinfo <1>:                          Implicit Variables.  (line  88)
+* makeinfo:                              Catalogue of Rules.  (line 158)
 * match-anything rule:                   Match-Anything Rules.
+                                                              (line   6)
 * match-anything rule, used to override: Overriding Makefiles.
-* missing features:                      Missing.
-* mistakes with wildcards:               Wildcard Pitfall.
-* modified variable reference:           Substitution Refs.
-* Modula-2, rule to compile:             Catalogue of Rules.
-* mostlyclean (standard target):         Goals.
-* multiple rules for one target:         Multiple Rules.
-* multiple rules for one target (::):    Double-Colon.
-* multiple targets:                      Multiple Targets.
-* multiple targets, in pattern rule:     Pattern Intro.
-* name of makefile:                      Makefile Names.
-* name of makefile, how to specify:      Makefile Names.
-* nested variable reference:             Computed Names.
-* newline, quoting, in commands:         Execution.
-* newline, quoting, in makefile:         Simple Makefile.
-* nondirectory part:                     File Name Functions.
-* normal prerequisites:                  Prerequisite Types.
-* OBJ:                                   Variables Simplify.
-* obj:                                   Variables Simplify.
-* OBJECTS:                               Variables Simplify.
-* objects:                               Variables Simplify.
-* OBJS:                                  Variables Simplify.
-* objs:                                  Variables Simplify.
-* old-fashioned suffix rules:            Suffix Rules.
-* options:                               Options Summary.
-* options, and recursion:                Options/Recursion.
-* options, setting from environment:     Options/Recursion.
-* options, setting in makefiles:         Options/Recursion.
-* order of pattern rules:                Pattern Intro.
-* order-only prerequisites:              Prerequisite Types.
-* origin of variable:                    Origin Function.
+                                                              (line  12)
+* missing features:                      Missing.             (line   6)
+* mistakes with wildcards:               Wildcard Pitfall.    (line   6)
+* modified variable reference:           Substitution Refs.   (line   6)
+* Modula-2, rule to compile:             Catalogue of Rules.  (line  74)
+* mostlyclean (standard target):         Goals.               (line  78)
+* multiple rules for one target:         Multiple Rules.      (line   6)
+* multiple rules for one target (::):    Double-Colon.        (line   6)
+* multiple targets:                      Multiple Targets.    (line   6)
+* multiple targets, in pattern rule:     Pattern Intro.       (line  49)
+* name of makefile:                      Makefile Names.      (line   6)
+* name of makefile, how to specify:      Makefile Names.      (line  30)
+* nested variable reference:             Computed Names.      (line   6)
+* newline, quoting, in commands:         Splitting Lines.     (line   6)
+* newline, quoting, in makefile:         Simple Makefile.     (line  40)
+* nondirectory part:                     File Name Functions. (line  27)
+* normal prerequisites:                  Prerequisite Types.  (line   6)
+* OBJ:                                   Variables Simplify.  (line  20)
+* obj:                                   Variables Simplify.  (line  20)
+* OBJECTS:                               Variables Simplify.  (line  20)
+* objects:                               Variables Simplify.  (line  14)
+* OBJS:                                  Variables Simplify.  (line  20)
+* objs:                                  Variables Simplify.  (line  20)
+* old-fashioned suffix rules:            Suffix Rules.        (line   6)
+* options:                               Options Summary.     (line   6)
+* options, and recursion:                Options/Recursion.   (line   6)
+* options, setting from environment:     Options/Recursion.   (line  81)
+* options, setting in makefiles:         Options/Recursion.   (line  81)
+* order of pattern rules:                Pattern Intro.       (line  57)
+* order-only prerequisites:              Prerequisite Types.  (line   6)
+* origin of variable:                    Origin Function.     (line   6)
 * overriding makefiles:                  Overriding Makefiles.
-* overriding variables with arguments:   Overriding.
-* overriding with override:              Override Directive.
-* parallel execution:                    Parallel.
-* parallel execution, and archive update: Archive Pitfalls.
-* parallel execution, overriding:        Special Targets.
-* parts of makefile rule:                Rule Introduction.
-* Pascal, rule to compile:               Catalogue of Rules.
-* pattern rule:                          Pattern Intro.
-* pattern rule, expansion:               Reading Makefiles.
-* pattern rules, order of:               Pattern Intro.
-* pattern rules, static (not implicit):  Static Pattern.
-* pattern rules, static, syntax of:      Static Usage.
-* pattern-specific variables:            Pattern-specific.
-* pc <1>:                                Implicit Variables.
-* pc:                                    Catalogue of Rules.
-* phony targets:                         Phony Targets.
-* pitfalls of wildcards:                 Wildcard Pitfall.
-* portability:                           Features.
-* POSIX:                                 Overview.
-* POSIX.2:                               Options/Recursion.
+                                                              (line   6)
+* overriding variables with arguments:   Overriding.          (line   6)
+* overriding with override:              Override Directive.  (line   6)
+* parallel execution:                    Parallel.            (line   6)
+* parallel execution, and archive update: Archive Pitfalls.   (line   6)
+* parallel execution, overriding:        Special Targets.     (line 135)
+* parts of makefile rule:                Rule Introduction.   (line   6)
+* Pascal, rule to compile:               Catalogue of Rules.  (line  45)
+* pattern rule:                          Pattern Intro.       (line   6)
+* pattern rule, expansion:               Reading Makefiles.   (line  62)
+* pattern rules, order of:               Pattern Intro.       (line  57)
+* pattern rules, static (not implicit):  Static Pattern.      (line   6)
+* pattern rules, static, syntax of:      Static Usage.        (line   6)
+* pattern-specific variables:            Pattern-specific.    (line   6)
+* pc <1>:                                Implicit Variables.  (line  84)
+* pc:                                    Catalogue of Rules.  (line  45)
+* phony targets:                         Phony Targets.       (line   6)
+* pitfalls of wildcards:                 Wildcard Pitfall.    (line   6)
+* portability:                           Features.            (line   6)
+* POSIX:                                 Overview.            (line  13)
+* POSIX.2:                               Options/Recursion.   (line  60)
 * post-installation commands:            Install Command Categories.
+                                                              (line   6)
 * pre-installation commands:             Install Command Categories.
-* precious targets:                      Special Targets.
-* predefined rules and variables, printing: Options Summary.
-* prefix, adding:                        File Name Functions.
-* prerequisite:                          Rules.
-* prerequisite pattern, implicit:        Pattern Intro.
-* prerequisite pattern, static (not implicit): Static Usage.
-* prerequisite types:                    Prerequisite Types.
-* prerequisite, expansion:               Reading Makefiles.
-* prerequisites:                         Rule Syntax.
+                                                              (line   6)
+* precious targets:                      Special Targets.     (line  29)
+* predefined rules and variables, printing: Options Summary.  (line 155)
+* prefix, adding:                        File Name Functions. (line  79)
+* prerequisite:                          Rules.               (line   6)
+* prerequisite pattern, implicit:        Pattern Intro.       (line  22)
+* prerequisite pattern, static (not implicit): Static Usage.  (line  30)
+* prerequisite types:                    Prerequisite Types.  (line   6)
+* prerequisite, expansion:               Reading Makefiles.   (line  62)
+* prerequisites:                         Rule Syntax.         (line  46)
 * prerequisites, and automatic variables: Automatic Variables.
+                                                              (line  17)
 * prerequisites, automatic generation <1>: Automatic Prerequisites.
-* prerequisites, automatic generation:   Include.
-* prerequisites, introduction to:        Rule Introduction.
-* prerequisites, list of all:            Automatic Variables.
-* prerequisites, list of changed:        Automatic Variables.
-* prerequisites, normal:                 Prerequisite Types.
-* prerequisites, order-only:             Prerequisite Types.
-* prerequisites, varying (static pattern): Static Pattern.
-* preserving intermediate files:         Chained Rules.
-* preserving with .PRECIOUS <1>:         Chained Rules.
-* preserving with .PRECIOUS:             Special Targets.
-* preserving with .SECONDARY:            Special Targets.
-* print (standard target):               Goals.
-* print target <1>:                      Empty Targets.
-* print target:                          Wildcard Examples.
-* printing directories:                  -w Option.
-* printing of commands:                  Echoing.
+                                                              (line   6)
+* prerequisites, automatic generation:   Include.             (line  50)
+* prerequisites, introduction to:        Rule Introduction.   (line   8)
+* prerequisites, list of all:            Automatic Variables. (line  61)
+* prerequisites, list of changed:        Automatic Variables. (line  51)
+* prerequisites, normal:                 Prerequisite Types.  (line   6)
+* prerequisites, order-only:             Prerequisite Types.  (line   6)
+* prerequisites, varying (static pattern): Static Pattern.    (line   6)
+* preserving intermediate files:         Chained Rules.       (line  46)
+* preserving with .PRECIOUS <1>:         Chained Rules.       (line  56)
+* preserving with .PRECIOUS:             Special Targets.     (line  29)
+* preserving with .SECONDARY:            Special Targets.     (line  49)
+* print (standard target):               Goals.               (line  97)
+* print target <1>:                      Empty Targets.       (line  25)
+* print target:                          Wildcard Examples.   (line  21)
+* printing directories:                  -w Option.           (line   6)
+* printing messages:                     Make Control Functions.
+                                                              (line  43)
+* printing of commands:                  Echoing.             (line   6)
 * printing user warnings:                Make Control Functions.
-* problems and bugs, reporting:          Bugs.
-* problems with wildcards:               Wildcard Pitfall.
-* processing a makefile:                 How Make Works.
+                                                              (line  35)
+* problems and bugs, reporting:          Bugs.                (line   6)
+* problems with wildcards:               Wildcard Pitfall.    (line   6)
+* processing a makefile:                 How Make Works.      (line   6)
 * question mode:                         Instead of Execution.
-* quoting %, in patsubst:                Text Functions.
-* quoting %, in static pattern:          Static Usage.
-* quoting %, in vpath:                   Selective Search.
-* quoting newline, in commands:          Execution.
-* quoting newline, in makefile:          Simple Makefile.
-* Ratfor, rule to compile:               Catalogue of Rules.
-* RCS, rule to extract from:             Catalogue of Rules.
-* reading makefiles:                     Reading Makefiles.
-* README:                                Makefile Names.
-* realclean (standard target):           Goals.
-* recompilation:                         Introduction.
+                                                              (line  25)
+* quoting %, in patsubst:                Text Functions.      (line  26)
+* quoting %, in static pattern:          Static Usage.        (line  37)
+* quoting %, in vpath:                   Selective Search.    (line  38)
+* quoting newline, in commands:          Splitting Lines.     (line   6)
+* quoting newline, in makefile:          Simple Makefile.     (line  40)
+* Ratfor, rule to compile:               Catalogue of Rules.  (line  49)
+* RCS, rule to extract from:             Catalogue of Rules.  (line 164)
+* reading makefiles:                     Reading Makefiles.   (line   6)
+* README:                                Makefile Names.      (line   9)
+* realclean (standard target):           Goals.               (line  85)
+* realpath:                              File Name Functions. (line 114)
+* recompilation:                         Introduction.        (line  22)
 * recompilation, avoiding:               Avoiding Compilation.
-* recording events with empty targets:   Empty Targets.
-* recursion:                             Recursion.
-* recursion, and -C:                     Options/Recursion.
-* recursion, and -f:                     Options/Recursion.
-* recursion, and -j:                     Options/Recursion.
-* recursion, and -o:                     Options/Recursion.
-* recursion, and -t:                     MAKE Variable.
-* recursion, and -w:                     -w Option.
-* recursion, and -W:                     Options/Recursion.
+                                                              (line   6)
+* recording events with empty targets:   Empty Targets.       (line   6)
+* recursion:                             Recursion.           (line   6)
+* recursion, and -C:                     Options/Recursion.   (line  22)
+* recursion, and -f:                     Options/Recursion.   (line  22)
+* recursion, and -j:                     Options/Recursion.   (line  25)
+* recursion, and -o:                     Options/Recursion.   (line  22)
+* recursion, and -t:                     MAKE Variable.       (line  34)
+* recursion, and -w:                     -w Option.           (line  20)
+* recursion, and -W:                     Options/Recursion.   (line  22)
 * recursion, and command line variable definitions: Options/Recursion.
-* recursion, and environment:            Variables/Recursion.
-* recursion, and MAKE variable:          MAKE Variable.
-* recursion, and MAKEFILES variable:     MAKEFILES Variable.
-* recursion, and options:                Options/Recursion.
-* recursion, and printing directories:   -w Option.
-* recursion, and variables:              Variables/Recursion.
-* recursion, level of:                   Variables/Recursion.
-* recursive variable expansion <1>:      Flavors.
-* recursive variable expansion:          Using Variables.
-* recursively expanded variables:        Flavors.
-* reference to variables <1>:            Advanced.
-* reference to variables:                Reference.
-* relinking:                             How Make Works.
-* remaking makefiles:                    Remaking Makefiles.
-* removal of target files <1>:           Interrupts.
-* removal of target files:               Errors.
-* removing duplicate words:              Text Functions.
-* removing targets on failure:           Special Targets.
-* removing, to clean up:                 Cleanup.
-* reporting bugs:                        Bugs.
-* rm:                                    Implicit Variables.
-* rm (shell command) <1>:                Errors.
-* rm (shell command) <2>:                Phony Targets.
-* rm (shell command) <3>:                Wildcard Examples.
-* rm (shell command):                    Simple Makefile.
-* rule commands:                         Commands.
-* rule prerequisites:                    Rule Syntax.
-* rule syntax:                           Rule Syntax.
-* rule targets:                          Rule Syntax.
-* rule, and $:                           Rule Syntax.
-* rule, double-colon (::):               Double-Colon.
-* rule, explicit, definition of:         Makefile Contents.
-* rule, how to write:                    Rules.
-* rule, implicit:                        Implicit Rules.
-* rule, implicit, and directory search:  Implicit/Search.
-* rule, implicit, and VPATH:             Implicit/Search.
-* rule, implicit, chains of:             Chained Rules.
-* rule, implicit, definition of:         Makefile Contents.
-* rule, implicit, how to use:            Using Implicit.
-* rule, implicit, introduction to:       make Deduces.
-* rule, implicit, predefined:            Catalogue of Rules.
-* rule, introduction to:                 Rule Introduction.
-* rule, multiple for one target:         Multiple Rules.
-* rule, no commands or prerequisites:    Force Targets.
-* rule, pattern:                         Pattern Intro.
-* rule, static pattern:                  Static Pattern.
+                                                              (line  17)
+* recursion, and environment:            Variables/Recursion. (line   6)
+* recursion, and MAKE variable:          MAKE Variable.       (line   6)
+* recursion, and MAKEFILES variable:     MAKEFILES Variable.  (line  14)
+* recursion, and options:                Options/Recursion.   (line   6)
+* recursion, and printing directories:   -w Option.           (line   6)
+* recursion, and variables:              Variables/Recursion. (line   6)
+* recursion, level of:                   Variables/Recursion. (line 115)
+* recursive variable expansion <1>:      Flavors.             (line   6)
+* recursive variable expansion:          Using Variables.     (line   6)
+* recursively expanded variables:        Flavors.             (line   6)
+* reference to variables <1>:            Advanced.            (line   6)
+* reference to variables:                Reference.           (line   6)
+* relinking:                             How Make Works.      (line  46)
+* remaking makefiles:                    Remaking Makefiles.  (line   6)
+* removal of target files <1>:           Interrupts.          (line   6)
+* removal of target files:               Errors.              (line  64)
+* removing duplicate words:              Text Functions.      (line 155)
+* removing targets on failure:           Special Targets.     (line  68)
+* removing, to clean up:                 Cleanup.             (line   6)
+* reporting bugs:                        Bugs.                (line   6)
+* rm:                                    Implicit Variables.  (line 110)
+* rm (shell command) <1>:                Errors.              (line  27)
+* rm (shell command) <2>:                Phony Targets.       (line  20)
+* rm (shell command) <3>:                Wildcard Examples.   (line  12)
+* rm (shell command):                    Simple Makefile.     (line  83)
+* rule commands:                         Commands.            (line   6)
+* rule prerequisites:                    Rule Syntax.         (line  46)
+* rule syntax:                           Rule Syntax.         (line   6)
+* rule targets:                          Rule Syntax.         (line  18)
+* rule, double-colon (::):               Double-Colon.        (line   6)
+* rule, explicit, definition of:         Makefile Contents.   (line  10)
+* rule, how to write:                    Rules.               (line   6)
+* rule, implicit:                        Implicit Rules.      (line   6)
+* rule, implicit, and directory search:  Implicit/Search.     (line   6)
+* rule, implicit, and VPATH:             Implicit/Search.     (line   6)
+* rule, implicit, chains of:             Chained Rules.       (line   6)
+* rule, implicit, definition of:         Makefile Contents.   (line  16)
+* rule, implicit, how to use:            Using Implicit.      (line   6)
+* rule, implicit, introduction to:       make Deduces.        (line   6)
+* rule, implicit, predefined:            Catalogue of Rules.  (line   6)
+* rule, introduction to:                 Rule Introduction.   (line   6)
+* rule, multiple for one target:         Multiple Rules.      (line   6)
+* rule, no commands or prerequisites:    Force Targets.       (line   6)
+* rule, pattern:                         Pattern Intro.       (line   6)
+* rule, static pattern:                  Static Pattern.      (line   6)
 * rule, static pattern versus implicit:  Static versus Implicit.
-* rule, with multiple targets:           Multiple Targets.
-* s. (SCCS file prefix):                 Catalogue of Rules.
-* SCCS, rule to extract from:            Catalogue of Rules.
+                                                              (line   6)
+* rule, with multiple targets:           Multiple Targets.    (line   6)
+* rules, and $:                          Rule Syntax.         (line  32)
+* s. (SCCS file prefix):                 Catalogue of Rules.  (line 173)
+* SCCS, rule to extract from:            Catalogue of Rules.  (line 173)
 * search algorithm, implicit rule:       Implicit Rule Search.
-* search path for prerequisites (VPATH): Directory Search.
+                                                              (line   6)
+* search path for prerequisites (VPATH): Directory Search.    (line   6)
 * search path for prerequisites (VPATH), and implicit rules: Implicit/Search.
+                                                              (line   6)
 * search path for prerequisites (VPATH), and link libraries: Libraries/Search.
-* searching for strings:                 Text Functions.
-* secondary files:                       Chained Rules.
-* secondary targets:                     Special Targets.
+                                                              (line   6)
+* searching for strings:                 Text Functions.      (line 103)
+* secondary expansion:                   Secondary Expansion. (line   6)
+* secondary expansion and explicit rules: Secondary Expansion.
+                                                              (line 106)
+* secondary expansion and implicit rules: Secondary Expansion.
+                                                              (line 146)
+* secondary expansion and static pattern rules: Secondary Expansion.
+                                                              (line 138)
+* secondary files:                       Chained Rules.       (line  46)
+* secondary targets:                     Special Targets.     (line  49)
 * sed (shell command):                   Automatic Prerequisites.
-* selecting a word:                      Text Functions.
-* selecting word lists:                  Text Functions.
-* sequences of commands:                 Sequences.
-* setting options from environment:      Options/Recursion.
-* setting options in makefiles:          Options/Recursion.
-* setting variables:                     Setting.
-* several rules for one target:          Multiple Rules.
-* several targets in a rule:             Multiple Targets.
-* shar (standard target):                Goals.
-* shell command:                         Simple Makefile.
-* shell command, and directory search:   Commands/Search.
-* shell command, execution:              Execution.
-* shell command, function for:           Shell Function.
-* shell file name pattern (in include):  Include.
-* shell wildcards (in include):          Include.
-* SHELL, MS-DOS specifics:               Execution.
-* signal:                                Interrupts.
-* silent operation:                      Echoing.
-* simple makefile:                       Simple Makefile.
-* simple variable expansion:             Using Variables.
-* simplifying with variables:            Variables Simplify.
-* simply expanded variables:             Flavors.
-* sorting words:                         Text Functions.
-* spaces, in variable values:            Flavors.
-* spaces, stripping:                     Text Functions.
-* special targets:                       Special Targets.
-* special variables:                     Special Variables.
-* specifying makefile name:              Makefile Names.
-* standard input:                        Parallel.
-* standards conformance:                 Overview.
+                                                              (line  73)
+* selecting a word:                      Text Functions.      (line 159)
+* selecting word lists:                  Text Functions.      (line 168)
+* sequences of commands:                 Sequences.           (line   6)
+* setting options from environment:      Options/Recursion.   (line  81)
+* setting options in makefiles:          Options/Recursion.   (line  81)
+* setting variables:                     Setting.             (line   6)
+* several rules for one target:          Multiple Rules.      (line   6)
+* several targets in a rule:             Multiple Targets.    (line   6)
+* shar (standard target):                Goals.               (line 103)
+* shell command:                         Simple Makefile.     (line  72)
+* shell command, and directory search:   Commands/Search.     (line   6)
+* shell command, execution:              Execution.           (line   6)
+* shell command, function for:           Shell Function.      (line   6)
+* shell file name pattern (in include):  Include.             (line  13)
+* shell variables, setting in commands:  Execution.           (line  10)
+* shell wildcards (in include):          Include.             (line  13)
+* shell, choosing the:                   Choosing the Shell.  (line   6)
+* SHELL, exported value:                 Variables/Recursion. (line  23)
+* SHELL, import from environment:        Environment.         (line  37)
+* shell, in DOS and Windows:             Choosing the Shell.  (line  36)
+* SHELL, MS-DOS specifics:               Choosing the Shell.  (line  42)
+* SHELL, value of:                       Choosing the Shell.  (line   6)
+* signal:                                Interrupts.          (line   6)
+* silent operation:                      Echoing.             (line   6)
+* simple makefile:                       Simple Makefile.     (line   6)
+* simple variable expansion:             Using Variables.     (line   6)
+* simplifying with variables:            Variables Simplify.  (line   6)
+* simply expanded variables:             Flavors.             (line  56)
+* sorting words:                         Text Functions.      (line 146)
+* spaces, in variable values:            Flavors.             (line 103)
+* spaces, stripping:                     Text Functions.      (line  80)
+* special targets:                       Special Targets.     (line   6)
+* special variables:                     Special Variables.   (line   6)
+* specifying makefile name:              Makefile Names.      (line  30)
+* splitting commands:                    Splitting Lines.     (line   6)
+* standard input:                        Parallel.            (line  30)
+* standards conformance:                 Overview.            (line  13)
 * standards for makefiles:               Makefile Conventions.
-* static pattern rule:                   Static Pattern.
-* static pattern rule, syntax of:        Static Usage.
+                                                              (line   6)
+* static pattern rule:                   Static Pattern.      (line   6)
+* static pattern rule, syntax of:        Static Usage.        (line   6)
 * static pattern rule, versus implicit:  Static versus Implicit.
-* stem <1>:                              Pattern Match.
-* stem:                                  Static Usage.
-* stem, variable for:                    Automatic Variables.
+                                                              (line   6)
+* static pattern rules, secondary expansion of: Secondary Expansion.
+                                                              (line 138)
+* stem <1>:                              Pattern Match.       (line   6)
+* stem:                                  Static Usage.        (line  17)
+* stem, variable for:                    Automatic Variables. (line  77)
 * stopping make:                         Make Control Functions.
-* strings, searching for:                Text Functions.
-* stripping whitespace:                  Text Functions.
-* sub-make:                              Variables/Recursion.
-* subdirectories, recursion for:         Recursion.
-* substitution variable reference:       Substitution Refs.
-* suffix rule:                           Suffix Rules.
+                                                              (line  11)
+* strings, searching for:                Text Functions.      (line 103)
+* stripping whitespace:                  Text Functions.      (line  80)
+* sub-make:                              Variables/Recursion. (line   6)
+* subdirectories, recursion for:         Recursion.           (line   6)
+* substitution variable reference:       Substitution Refs.   (line   6)
+* suffix rule:                           Suffix Rules.        (line   6)
 * suffix rule, for archive:              Archive Suffix Rules.
-* suffix, adding:                        File Name Functions.
-* suffix, function to find:              File Name Functions.
-* suffix, substituting in variables:     Substitution Refs.
-* switches:                              Options Summary.
-* symbol directories, updating archive:  Archive Symbols.
-* syntax of rules:                       Rule Syntax.
-* tab character (in commands):           Rule Syntax.
-* tabs in rules:                         Rule Introduction.
-* TAGS (standard target):                Goals.
-* tangle <1>:                            Implicit Variables.
-* tangle:                                Catalogue of Rules.
-* tar (standard target):                 Goals.
-* target:                                Rules.
-* target pattern, implicit:              Pattern Intro.
-* target pattern, static (not implicit): Static Usage.
-* target, deleting on error:             Errors.
-* target, deleting on interrupt:         Interrupts.
-* target, expansion:                     Reading Makefiles.
-* target, multiple in pattern rule:      Pattern Intro.
-* target, multiple rules for one:        Multiple Rules.
+                                                              (line   6)
+* suffix, adding:                        File Name Functions. (line  68)
+* suffix, function to find:              File Name Functions. (line  43)
+* suffix, substituting in variables:     Substitution Refs.   (line   6)
+* switches:                              Options Summary.     (line   6)
+* symbol directories, updating archive:  Archive Symbols.     (line   6)
+* syntax of commands:                    Command Syntax.      (line   6)
+* syntax of rules:                       Rule Syntax.         (line   6)
+* tab character (in commands):           Rule Syntax.         (line  26)
+* tabs in rules:                         Rule Introduction.   (line  21)
+* TAGS (standard target):                Goals.               (line 111)
+* tangle <1>:                            Implicit Variables.  (line 104)
+* tangle:                                Catalogue of Rules.  (line 151)
+* tar (standard target):                 Goals.               (line 100)
+* target:                                Rules.               (line   6)
+* target pattern, implicit:              Pattern Intro.       (line   9)
+* target pattern, static (not implicit): Static Usage.        (line  17)
+* target, deleting on error:             Errors.              (line  64)
+* target, deleting on interrupt:         Interrupts.          (line   6)
+* target, expansion:                     Reading Makefiles.   (line  62)
+* target, multiple in pattern rule:      Pattern Intro.       (line  49)
+* target, multiple rules for one:        Multiple Rules.      (line   6)
 * target, touching:                      Instead of Execution.
-* target-specific variables:             Target-specific.
-* targets:                               Rule Syntax.
-* targets without a file:                Phony Targets.
-* targets, built-in special:             Special Targets.
-* targets, empty:                        Empty Targets.
-* targets, force:                        Force Targets.
-* targets, introduction to:              Rule Introduction.
-* targets, multiple:                     Multiple Targets.
-* targets, phony:                        Phony Targets.
+                                                              (line  19)
+* target-specific variables:             Target-specific.     (line   6)
+* targets:                               Rule Syntax.         (line  18)
+* targets without a file:                Phony Targets.       (line   6)
+* targets, built-in special:             Special Targets.     (line   6)
+* targets, empty:                        Empty Targets.       (line   6)
+* targets, force:                        Force Targets.       (line   6)
+* targets, introduction to:              Rule Introduction.   (line   8)
+* targets, multiple:                     Multiple Targets.    (line   6)
+* targets, phony:                        Phony Targets.       (line   6)
 * terminal rule:                         Match-Anything Rules.
-* test (standard target):                Goals.
-* testing compilation:                   Testing.
-* tex <1>:                               Implicit Variables.
-* tex:                                   Catalogue of Rules.
-* TeX, rule to run:                      Catalogue of Rules.
-* texi2dvi <1>:                          Implicit Variables.
-* texi2dvi:                              Catalogue of Rules.
-* Texinfo, rule to format:               Catalogue of Rules.
-* tilde (~):                             Wildcards.
-* touch (shell command) <1>:             Empty Targets.
-* touch (shell command):                 Wildcard Examples.
+                                                              (line   6)
+* test (standard target):                Goals.               (line 115)
+* testing compilation:                   Testing.             (line   6)
+* tex <1>:                               Implicit Variables.  (line  91)
+* tex:                                   Catalogue of Rules.  (line 151)
+* TeX, rule to run:                      Catalogue of Rules.  (line 151)
+* texi2dvi <1>:                          Implicit Variables.  (line  95)
+* texi2dvi:                              Catalogue of Rules.  (line 158)
+* Texinfo, rule to format:               Catalogue of Rules.  (line 158)
+* tilde (~):                             Wildcards.           (line  11)
+* touch (shell command) <1>:             Empty Targets.       (line  25)
+* touch (shell command):                 Wildcard Examples.   (line  21)
 * touching files:                        Instead of Execution.
-* traditional directory search (GPATH):  Search Algorithm.
-* types of prerequisites:                Prerequisite Types.
-* undefined variables, warning message:  Options Summary.
-* updating archive symbol directories:   Archive Symbols.
-* updating makefiles:                    Remaking Makefiles.
-* user defined functions:                Call Function.
-* value:                                 Using Variables.
-* value, how a variable gets it:         Values.
-* variable:                              Using Variables.
-* variable definition:                   Makefile Contents.
-* variables:                             Variables Simplify.
-* variables, $ in name:                  Computed Names.
-* variables, and implicit rule:          Automatic Variables.
-* variables, appending to:               Appending.
-* variables, automatic:                  Automatic Variables.
-* variables, command line:               Overriding.
-* variables, command line, and recursion: Options/Recursion.
-* variables, computed names:             Computed Names.
-* variables, conditional assignment:     Flavors.
-* variables, defining verbatim:          Defining.
-* variables, environment <1>:            Environment.
-* variables, environment:                Variables/Recursion.
-* variables, exporting:                  Variables/Recursion.
-* variables, flavors:                    Flavors.
-* variables, how they get their values:  Values.
-* variables, how to reference:           Reference.
-* variables, loops in expansion:         Flavors.
-* variables, modified reference:         Substitution Refs.
-* variables, nested references:          Computed Names.
-* variables, origin of:                  Origin Function.
-* variables, overriding:                 Override Directive.
-* variables, overriding with arguments:  Overriding.
-* variables, pattern-specific:           Pattern-specific.
-* variables, recursively expanded:       Flavors.
-* variables, setting:                    Setting.
-* variables, simply expanded:            Flavors.
-* variables, spaces in values:           Flavors.
-* variables, substituting suffix in:     Substitution Refs.
-* variables, substitution reference:     Substitution Refs.
-* variables, target-specific:            Target-specific.
-* variables, unexpanded value:           Value Function.
-* variables, warning for undefined:      Options Summary.
-* varying prerequisites:                 Static Pattern.
-* verbatim variable definition:          Defining.
-* vpath:                                 Directory Search.
-* VPATH, and implicit rules:             Implicit/Search.
-* VPATH, and link libraries:             Libraries/Search.
+                                                              (line  19)
+* traditional directory search (GPATH):  Search Algorithm.    (line  42)
+* types of prerequisites:                Prerequisite Types.  (line   6)
+* undefined variables, warning message:  Options Summary.     (line 251)
+* updating archive symbol directories:   Archive Symbols.     (line   6)
+* updating makefiles:                    Remaking Makefiles.  (line   6)
+* user defined functions:                Call Function.       (line   6)
+* value:                                 Using Variables.     (line   6)
+* value, how a variable gets it:         Values.              (line   6)
+* variable:                              Using Variables.     (line   6)
+* variable definition:                   Makefile Contents.   (line  22)
+* variable references in commands:       Variables in Commands.
+                                                              (line   6)
+* variables:                             Variables Simplify.  (line   6)
+* variables, $ in name:                  Computed Names.      (line   6)
+* variables, and implicit rule:          Automatic Variables. (line   6)
+* variables, appending to:               Appending.           (line   6)
+* variables, automatic:                  Automatic Variables. (line   6)
+* variables, command line:               Overriding.          (line   6)
+* variables, command line, and recursion: Options/Recursion.  (line  17)
+* variables, computed names:             Computed Names.      (line   6)
+* variables, conditional assignment:     Flavors.             (line 129)
+* variables, defining verbatim:          Defining.            (line   6)
+* variables, environment <1>:            Environment.         (line   6)
+* variables, environment:                Variables/Recursion. (line   6)
+* variables, exporting:                  Variables/Recursion. (line   6)
+* variables, flavor of:                  Flavor Function.     (line   6)
+* variables, flavors:                    Flavors.             (line   6)
+* variables, how they get their values:  Values.              (line   6)
+* variables, how to reference:           Reference.           (line   6)
+* variables, loops in expansion:         Flavors.             (line  44)
+* variables, modified reference:         Substitution Refs.   (line   6)
+* variables, nested references:          Computed Names.      (line   6)
+* variables, origin of:                  Origin Function.     (line   6)
+* variables, overriding:                 Override Directive.  (line   6)
+* variables, overriding with arguments:  Overriding.          (line   6)
+* variables, pattern-specific:           Pattern-specific.    (line   6)
+* variables, recursively expanded:       Flavors.             (line   6)
+* variables, setting:                    Setting.             (line   6)
+* variables, simply expanded:            Flavors.             (line  56)
+* variables, spaces in values:           Flavors.             (line 103)
+* variables, substituting suffix in:     Substitution Refs.   (line   6)
+* variables, substitution reference:     Substitution Refs.   (line   6)
+* variables, target-specific:            Target-specific.     (line   6)
+* variables, unexpanded value:           Value Function.      (line   6)
+* variables, warning for undefined:      Options Summary.     (line 251)
+* varying prerequisites:                 Static Pattern.      (line   6)
+* verbatim variable definition:          Defining.            (line   6)
+* vpath:                                 Directory Search.    (line   6)
+* VPATH, and implicit rules:             Implicit/Search.     (line   6)
+* VPATH, and link libraries:             Libraries/Search.    (line   6)
 * warnings, printing:                    Make Control Functions.
-* weave <1>:                             Implicit Variables.
-* weave:                                 Catalogue of Rules.
-* Web, rule to run:                      Catalogue of Rules.
+                                                              (line  35)
+* weave <1>:                             Implicit Variables.  (line  98)
+* weave:                                 Catalogue of Rules.  (line 151)
+* Web, rule to run:                      Catalogue of Rules.  (line 151)
 * what if:                               Instead of Execution.
-* whitespace, in variable values:        Flavors.
-* whitespace, stripping:                 Text Functions.
-* wildcard:                              Wildcards.
-* wildcard pitfalls:                     Wildcard Pitfall.
-* wildcard, function:                    File Name Functions.
-* wildcard, in archive member:           Archive Members.
-* wildcard, in include:                  Include.
+                                                              (line  33)
+* whitespace, in variable values:        Flavors.             (line 103)
+* whitespace, stripping:                 Text Functions.      (line  80)
+* wildcard:                              Wildcards.           (line   6)
+* wildcard pitfalls:                     Wildcard Pitfall.    (line   6)
+* wildcard, function:                    File Name Functions. (line 107)
+* wildcard, in archive member:           Archive Members.     (line  36)
+* wildcard, in include:                  Include.             (line  13)
 * wildcards and MS-DOS/MS-Windows backslashes: Wildcard Pitfall.
-* word, selecting a:                     Text Functions.
-* words, extracting first:               Text Functions.
-* words, filtering:                      Text Functions.
-* words, filtering out:                  Text Functions.
-* words, finding number:                 Text Functions.
-* words, iterating over:                 Foreach Function.
-* words, joining lists:                  File Name Functions.
-* words, removing duplicates:            Text Functions.
-* words, selecting lists of:             Text Functions.
-* writing rule commands:                 Commands.
-* writing rules:                         Rules.
-* yacc <1>:                              Implicit Variables.
-* yacc <2>:                              Catalogue of Rules.
-* yacc:                                  Sequences.
-* Yacc, rule to run:                     Catalogue of Rules.
-* ~ (tilde):                             Wildcards.
+                                                              (line  31)
+* Windows, choosing a shell in:          Choosing the Shell.  (line  36)
+* word, selecting a:                     Text Functions.      (line 159)
+* words, extracting first:               Text Functions.      (line 184)
+* words, extracting last:                Text Functions.      (line 197)
+* words, filtering:                      Text Functions.      (line 114)
+* words, filtering out:                  Text Functions.      (line 132)
+* words, finding number:                 Text Functions.      (line 180)
+* words, iterating over:                 Foreach Function.    (line   6)
+* words, joining lists:                  File Name Functions. (line  90)
+* words, removing duplicates:            Text Functions.      (line 155)
+* words, selecting lists of:             Text Functions.      (line 168)
+* writing rule commands:                 Commands.            (line   6)
+* writing rules:                         Rules.               (line   6)
+* yacc <1>:                              Implicit Variables.  (line  75)
+* yacc <2>:                              Catalogue of Rules.  (line 120)
+* yacc:                                  Sequences.           (line  18)
+* Yacc, rule to run:                     Catalogue of Rules.  (line 120)
+* ~ (tilde):                             Wildcards.           (line  11)
 
 
@@ -3307 +4181 @@
 *******************************************
 
+[index]
 * Menu:
 
-* $$(@D):                                Automatic Variables.
-* $$(@F):                                Automatic Variables.
-* $$@:                                   Automatic Variables.
-* $%:                                    Automatic Variables.
-* $(%D):                                 Automatic Variables.
-* $(%F):                                 Automatic Variables.
-* $(*D):                                 Automatic Variables.
-* $(*F):                                 Automatic Variables.
-* $(+D):                                 Automatic Variables.
-* $(+F):                                 Automatic Variables.
-* $(.VARIABLES):                         Special Variables.
-* $(<D):                                 Automatic Variables.
-* $(<F):                                 Automatic Variables.
-* $(?D):                                 Automatic Variables.
-* $(?F):                                 Automatic Variables.
-* $(@D):                                 Automatic Variables.
-* $(@F):                                 Automatic Variables.
-* $(^D):                                 Automatic Variables.
-* $(^F):                                 Automatic Variables.
-* $*:                                    Automatic Variables.
-* $*, and static pattern:                Static Usage.
-* $+:                                    Automatic Variables.
-* $<:                                    Automatic Variables.
-* $?:                                    Automatic Variables.
-* $@:                                    Automatic Variables.
-* $^:                                    Automatic Variables.
-* % (automatic variable):                Automatic Variables.
-* %D (automatic variable):               Automatic Variables.
-* %F (automatic variable):               Automatic Variables.
-* * (automatic variable):                Automatic Variables.
-* * (automatic variable), unsupported bizarre usage: Missing.
-* *D (automatic variable):               Automatic Variables.
-* *F (automatic variable):               Automatic Variables.
-* + (automatic variable):                Automatic Variables.
-* +D (automatic variable):               Automatic Variables.
-* +F (automatic variable):               Automatic Variables.
-* .DEFAULT <1>:                          Last Resort.
-* .DEFAULT:                              Special Targets.
-* .DEFAULT, and empty commands:          Empty Commands.
-* .DELETE_ON_ERROR <1>:                  Errors.
-* .DELETE_ON_ERROR:                      Special Targets.
-* .EXPORT_ALL_VARIABLES <1>:             Variables/Recursion.
-* .EXPORT_ALL_VARIABLES:                 Special Targets.
-* .IGNORE <1>:                           Errors.
-* .IGNORE:                               Special Targets.
-* .INTERMEDIATE:                         Special Targets.
-* .LIBPATTERNS:                          Libraries/Search.
-* .LOW_RESOLUTION_TIME:                  Special Targets.
-* .NOTPARALLEL:                          Special Targets.
-* .PHONY <1>:                            Special Targets.
-* .PHONY:                                Phony Targets.
-* .POSIX:                                Options/Recursion.
-* .PRECIOUS <1>:                         Interrupts.
-* .PRECIOUS:                             Special Targets.
-* .SECONDARY:                            Special Targets.
-* .SILENT <1>:                           Echoing.
-* .SILENT:                               Special Targets.
-* .SUFFIXES <1>:                         Suffix Rules.
-* .SUFFIXES:                             Special Targets.
-* .VARIABLES (list of variables):        Special Variables.
-* /usr/gnu/include:                      Include.
-* /usr/include:                          Include.
-* /usr/local/include:                    Include.
-* < (automatic variable):                Automatic Variables.
-* <D (automatic variable):               Automatic Variables.
-* <F (automatic variable):               Automatic Variables.
-* ? (automatic variable):                Automatic Variables.
-* ?D (automatic variable):               Automatic Variables.
-* ?F (automatic variable):               Automatic Variables.
-* @ (automatic variable):                Automatic Variables.
-* @D (automatic variable):               Automatic Variables.
-* @F (automatic variable):               Automatic Variables.
-* ^ (automatic variable):                Automatic Variables.
-* ^D (automatic variable):               Automatic Variables.
-* ^F (automatic variable):               Automatic Variables.
-* addprefix:                             File Name Functions.
-* addsuffix:                             File Name Functions.
-* AR:                                    Implicit Variables.
-* ARFLAGS:                               Implicit Variables.
-* AS:                                    Implicit Variables.
-* ASFLAGS:                               Implicit Variables.
-* basename:                              File Name Functions.
-* bindir:                                Directory Variables.
-* call:                                  Call Function.
-* CC:                                    Implicit Variables.
-* CFLAGS:                                Implicit Variables.
-* CO:                                    Implicit Variables.
-* COFLAGS:                               Implicit Variables.
-* COMSPEC:                               Execution.
-* CPP:                                   Implicit Variables.
-* CPPFLAGS:                              Implicit Variables.
-* CTANGLE:                               Implicit Variables.
-* CURDIR:                                Recursion.
-* CWEAVE:                                Implicit Variables.
-* CXX:                                   Implicit Variables.
-* CXXFLAGS:                              Implicit Variables.
-* define:                                Defining.
-* dir:                                   File Name Functions.
-* else:                                  Conditional Syntax.
-* endef:                                 Defining.
-* endif:                                 Conditional Syntax.
+* $%:                                    Automatic Variables. (line  37)
+* $(%D):                                 Automatic Variables. (line 129)
+* $(%F):                                 Automatic Variables. (line 130)
+* $(*D):                                 Automatic Variables. (line 124)
+* $(*F):                                 Automatic Variables. (line 125)
+* $(+D):                                 Automatic Variables. (line 147)
+* $(+F):                                 Automatic Variables. (line 148)
+* $(<D):                                 Automatic Variables. (line 137)
+* $(<F):                                 Automatic Variables. (line 138)
+* $(?D):                                 Automatic Variables. (line 153)
+* $(?F):                                 Automatic Variables. (line 154)
+* $(@D):                                 Automatic Variables. (line 113)
+* $(@F):                                 Automatic Variables. (line 119)
+* $(^D):                                 Automatic Variables. (line 142)
+* $(^F):                                 Automatic Variables. (line 143)
+* $*:                                    Automatic Variables. (line  73)
+* $*, and static pattern:                Static Usage.        (line  81)
+* $+:                                    Automatic Variables. (line  63)
+* $<:                                    Automatic Variables. (line  43)
+* $?:                                    Automatic Variables. (line  48)
+* $@:                                    Automatic Variables. (line  30)
+* $^:                                    Automatic Variables. (line  53)
+* $|:                                    Automatic Variables. (line  69)
+* % (automatic variable):                Automatic Variables. (line  37)
+* %D (automatic variable):               Automatic Variables. (line 129)
+* %F (automatic variable):               Automatic Variables. (line 130)
+* * (automatic variable):                Automatic Variables. (line  73)
+* * (automatic variable), unsupported bizarre usage: Missing. (line  44)
+* *D (automatic variable):               Automatic Variables. (line 124)
+* *F (automatic variable):               Automatic Variables. (line 125)
+* + (automatic variable):                Automatic Variables. (line  63)
+* +D (automatic variable):               Automatic Variables. (line 147)
+* +F (automatic variable):               Automatic Variables. (line 148)
+* .DEFAULT <1>:                          Last Resort.         (line  23)
+* .DEFAULT:                              Special Targets.     (line  20)
+* .DEFAULT, and empty commands:          Empty Commands.      (line  16)
+* .DEFAULT_GOAL (define default goal):   Special Variables.   (line  10)
+* .DELETE_ON_ERROR <1>:                  Errors.              (line  64)
+* .DELETE_ON_ERROR:                      Special Targets.     (line  67)
+* .EXPORT_ALL_VARIABLES <1>:             Variables/Recursion. (line  99)
+* .EXPORT_ALL_VARIABLES:                 Special Targets.     (line 129)
+* .FEATURES (list of supported features): Special Variables.  (line  65)
+* .IGNORE <1>:                           Errors.              (line  30)
+* .IGNORE:                               Special Targets.     (line  74)
+* .INCLUDE_DIRS (list of include directories): Special Variables.
+                                                              (line  98)
+* .INTERMEDIATE:                         Special Targets.     (line  43)
+* .LIBPATTERNS:                          Libraries/Search.    (line   6)
+* .LOW_RESOLUTION_TIME:                  Special Targets.     (line  86)
+* .NOTPARALLEL:                          Special Targets.     (line 134)
+* .PHONY <1>:                            Special Targets.     (line   8)
+* .PHONY:                                Phony Targets.       (line  22)
+* .POSIX:                                Options/Recursion.   (line  60)
+* .PRECIOUS <1>:                         Interrupts.          (line  22)
+* .PRECIOUS:                             Special Targets.     (line  28)
+* .SECONDARY:                            Special Targets.     (line  48)
+* .SECONDEXPANSION <1>:                  Special Targets.     (line  57)
+* .SECONDEXPANSION:                      Secondary Expansion. (line   6)
+* .SILENT <1>:                           Echoing.             (line  24)
+* .SILENT:                               Special Targets.     (line 116)
+* .SUFFIXES <1>:                         Suffix Rules.        (line  61)
+* .SUFFIXES:                             Special Targets.     (line  15)
+* .VARIABLES (list of variables):        Special Variables.   (line  56)
+* /usr/gnu/include:                      Include.             (line  52)
+* /usr/include:                          Include.             (line  52)
+* /usr/local/include:                    Include.             (line  52)
+* < (automatic variable):                Automatic Variables. (line  43)
+* <D (automatic variable):               Automatic Variables. (line 137)
+* <F (automatic variable):               Automatic Variables. (line 138)
+* ? (automatic variable):                Automatic Variables. (line  48)
+* ?D (automatic variable):               Automatic Variables. (line 153)
+* ?F (automatic variable):               Automatic Variables. (line 154)
+* @ (automatic variable):                Automatic Variables. (line  30)
+* @D (automatic variable):               Automatic Variables. (line 113)
+* @F (automatic variable):               Automatic Variables. (line 119)
+* ^ (automatic variable):                Automatic Variables. (line  53)
+* ^D (automatic variable):               Automatic Variables. (line 142)
+* ^F (automatic variable):               Automatic Variables. (line 143)
+* abspath:                               File Name Functions. (line 121)
+* addprefix:                             File Name Functions. (line  79)
+* addsuffix:                             File Name Functions. (line  68)
+* and:                                   Conditional Functions.
+                                                              (line  45)
+* AR:                                    Implicit Variables.  (line  41)
+* ARFLAGS:                               Implicit Variables.  (line 117)
+* AS:                                    Implicit Variables.  (line  44)
+* ASFLAGS:                               Implicit Variables.  (line 120)
+* basename:                              File Name Functions. (line  57)
+* bindir:                                Directory Variables. (line  53)
+* call:                                  Call Function.       (line   6)
+* CC:                                    Implicit Variables.  (line  47)
+* CFLAGS:                                Implicit Variables.  (line 124)
+* CO:                                    Implicit Variables.  (line  50)
+* COFLAGS:                               Implicit Variables.  (line 130)
+* COMSPEC:                               Choosing the Shell.  (line  39)
+* CPP:                                   Implicit Variables.  (line  59)
+* CPPFLAGS:                              Implicit Variables.  (line 133)
+* CTANGLE:                               Implicit Variables.  (line 107)
+* CURDIR:                                Recursion.           (line  28)
+* CWEAVE:                                Implicit Variables.  (line 101)
+* CXX:                                   Implicit Variables.  (line  53)
+* CXXFLAGS:                              Implicit Variables.  (line 127)
+* define:                                Defining.            (line   6)
+* dir:                                   File Name Functions. (line  17)
+* else:                                  Conditional Syntax.  (line   6)
+* endef:                                 Defining.            (line   6)
+* endif:                                 Conditional Syntax.  (line   6)
 * error:                                 Make Control Functions.
-* eval:                                  Eval Function.
-* exec_prefix:                           Directory Variables.
-* export:                                Variables/Recursion.
-* FC:                                    Implicit Variables.
-* FFLAGS:                                Implicit Variables.
-* filter:                                Text Functions.
-* filter-out:                            Text Functions.
-* findstring:                            Text Functions.
-* firstword:                             Text Functions.
-* foreach:                               Foreach Function.
-* GET:                                   Implicit Variables.
-* GFLAGS:                                Implicit Variables.
-* GNUmakefile:                           Makefile Names.
-* GPATH:                                 Search Algorithm.
-* if:                                    If Function.
-* ifdef:                                 Conditional Syntax.
-* ifeq:                                  Conditional Syntax.
-* ifndef:                                Conditional Syntax.
-* ifneq:                                 Conditional Syntax.
-* include:                               Include.
-* join:                                  File Name Functions.
-* LDFLAGS:                               Implicit Variables.
-* LEX:                                   Implicit Variables.
-* LFLAGS:                                Implicit Variables.
-* libexecdir:                            Directory Variables.
-* MAKE <1>:                              Flavors.
-* MAKE:                                  MAKE Variable.
-* MAKECMDGOALS:                          Goals.
-* makefile:                              Makefile Names.
-* Makefile:                              Makefile Names.
-* MAKEFILES <1>:                         Variables/Recursion.
-* MAKEFILES:                             MAKEFILES Variable.
-* MAKEFLAGS:                             Options/Recursion.
-* MAKEINFO:                              Implicit Variables.
-* MAKELEVEL <1>:                         Flavors.
-* MAKELEVEL:                             Variables/Recursion.
-* MAKEOVERRIDES:                         Options/Recursion.
-* MFLAGS:                                Options/Recursion.
-* notdir:                                File Name Functions.
-* origin:                                Origin Function.
-* OUTPUT_OPTION:                         Catalogue of Rules.
-* override:                              Override Directive.
-* patsubst <1>:                          Text Functions.
-* patsubst:                              Substitution Refs.
-* PC:                                    Implicit Variables.
-* PFLAGS:                                Implicit Variables.
-* prefix:                                Directory Variables.
-* RFLAGS:                                Implicit Variables.
-* RM:                                    Implicit Variables.
-* sbindir:                               Directory Variables.
-* shell:                                 Shell Function.
-* SHELL:                                 Execution.
-* SHELL (command execution):             Execution.
-* sort:                                  Text Functions.
-* strip:                                 Text Functions.
-* subst <1>:                             Text Functions.
-* subst:                                 Multiple Targets.
-* suffix:                                File Name Functions.
-* SUFFIXES:                              Suffix Rules.
-* TANGLE:                                Implicit Variables.
-* TEX:                                   Implicit Variables.
-* TEXI2DVI:                              Implicit Variables.
-* unexport:                              Variables/Recursion.
-* value:                                 Value Function.
-* vpath:                                 Selective Search.
-* VPATH:                                 General Search.
-* vpath:                                 Directory Search.
-* VPATH:                                 Directory Search.
+                                                              (line  11)
+* eval:                                  Eval Function.       (line   6)
+* exec_prefix:                           Directory Variables. (line  35)
+* export:                                Variables/Recursion. (line  40)
+* FC:                                    Implicit Variables.  (line  63)
+* FFLAGS:                                Implicit Variables.  (line 137)
+* filter:                                Text Functions.      (line 114)
+* filter-out:                            Text Functions.      (line 132)
+* findstring:                            Text Functions.      (line 103)
+* firstword:                             Text Functions.      (line 184)
+* flavor:                                Flavor Function.     (line   6)
+* foreach:                               Foreach Function.    (line   6)
+* GET:                                   Implicit Variables.  (line  67)
+* GFLAGS:                                Implicit Variables.  (line 140)
+* GNUmakefile:                           Makefile Names.      (line   7)
+* GPATH:                                 Search Algorithm.    (line  48)
+* if:                                    Conditional Functions.
+                                                              (line   6)
+* ifdef:                                 Conditional Syntax.  (line   6)
+* ifeq:                                  Conditional Syntax.  (line   6)
+* ifndef:                                Conditional Syntax.  (line   6)
+* ifneq:                                 Conditional Syntax.  (line   6)
+* include:                               Include.             (line   6)
+* info:                                  Make Control Functions.
+                                                              (line  43)
+* join:                                  File Name Functions. (line  90)
+* lastword:                              Text Functions.      (line 197)
+* LDFLAGS:                               Implicit Variables.  (line 143)
+* LEX:                                   Implicit Variables.  (line  70)
+* LFLAGS:                                Implicit Variables.  (line 147)
+* libexecdir:                            Directory Variables. (line  66)
+* LINT:                                  Implicit Variables.  (line  78)
+* LINTFLAGS:                             Implicit Variables.  (line 159)
+* M2C:                                   Implicit Variables.  (line  81)
+* MAKE <1>:                              Flavors.             (line  84)
+* MAKE:                                  MAKE Variable.       (line   6)
+* MAKE_RESTARTS (number of times make has restarted): Special Variables.
+                                                              (line  49)
+* MAKE_VERSION:                          Features.            (line 197)
+* MAKECMDGOALS:                          Goals.               (line  30)
+* makefile:                              Makefile Names.      (line   7)
+* Makefile:                              Makefile Names.      (line   7)
+* MAKEFILE_LIST:                         MAKEFILE_LIST Variable.
+                                                              (line   6)
+* MAKEFILES <1>:                         Variables/Recursion. (line 127)
+* MAKEFILES:                             MAKEFILES Variable.  (line   6)
+* MAKEFLAGS:                             Options/Recursion.   (line   6)
+* MAKEINFO:                              Implicit Variables.  (line  87)
+* MAKELEVEL <1>:                         Flavors.             (line  84)
+* MAKELEVEL:                             Variables/Recursion. (line 115)
+* MAKEOVERRIDES:                         Options/Recursion.   (line  49)
+* MAKESHELL (MS-DOS alternative to SHELL): Choosing the Shell.
+                                                              (line  25)
+* MFLAGS:                                Options/Recursion.   (line  65)
+* notdir:                                File Name Functions. (line  27)
+* or:                                    Conditional Functions.
+                                                              (line  37)
+* origin:                                Origin Function.     (line   6)
+* OUTPUT_OPTION:                         Catalogue of Rules.  (line 202)
+* override:                              Override Directive.  (line   6)
+* patsubst <1>:                          Text Functions.      (line  18)
+* patsubst:                              Substitution Refs.   (line  28)
+* PC:                                    Implicit Variables.  (line  84)
+* PFLAGS:                                Implicit Variables.  (line 153)
+* prefix:                                Directory Variables. (line  25)
+* realpath:                              File Name Functions. (line 114)
+* RFLAGS:                                Implicit Variables.  (line 156)
+* RM:                                    Implicit Variables.  (line 110)
+* sbindir:                               Directory Variables. (line  59)
+* shell:                                 Shell Function.      (line   6)
+* SHELL:                                 Choosing the Shell.  (line   6)
+* SHELL (command execution):             Execution.           (line   6)
+* sort:                                  Text Functions.      (line 146)
+* strip:                                 Text Functions.      (line  80)
+* subst <1>:                             Text Functions.      (line   9)
+* subst:                                 Multiple Targets.    (line  28)
+* suffix:                                File Name Functions. (line  43)
+* SUFFIXES:                              Suffix Rules.        (line  81)
+* TANGLE:                                Implicit Variables.  (line 104)
+* TEX:                                   Implicit Variables.  (line  91)
+* TEXI2DVI:                              Implicit Variables.  (line  94)
+* unexport:                              Variables/Recursion. (line  45)
+* value:                                 Value Function.      (line   6)
+* vpath:                                 Selective Search.    (line   6)
+* VPATH:                                 General Search.      (line   6)
+* vpath:                                 Directory Search.    (line   6)
+* VPATH:                                 Directory Search.    (line   6)
 * warning:                               Make Control Functions.
-* WEAVE:                                 Implicit Variables.
-* wildcard <1>:                          File Name Functions.
-* wildcard:                              Wildcard Function.
-* word:                                  Text Functions.
-* wordlist:                              Text Functions.
-* words:                                 Text Functions.
-* YACC:                                  Implicit Variables.
-* YACCR:                                 Implicit Variables.
-* YFLAGS:                                Implicit Variables.
-
-
+                                                              (line  35)
+* WEAVE:                                 Implicit Variables.  (line  98)
+* wildcard <1>:                          File Name Functions. (line 107)
+* wildcard:                              Wildcard Function.   (line   6)
+* word:                                  Text Functions.      (line 159)
+* wordlist:                              Text Functions.      (line 168)
+* words:                                 Text Functions.      (line 180)
+* YACC:                                  Implicit Variables.  (line  74)
+* YFLAGS:                                Implicit Variables.  (line 150)
+* | (automatic variable):                Automatic Variables. (line  69)
+
+

vendor/gnumake/current/doc/make.texi

@@ -2 +2 @@
 @c %**start of header
 @setfilename make.info
+
+@include version.texi
+@set EDITION 0.70
+@set RCSID $Id: make.texi,v 1.45 2006/04/01 06:36:40 psmith Exp $
+
 @settitle GNU @code{make}
 @setchapternewpage odd
-@c %**end of header
-
-@c FSF publishers: format makebook.texi instead of using this file directly.
-
-@set RCSID $Id: make.texi,v 1.30 2005/05/13 12:45:31 psmith Exp $
-@set EDITION 0.70
-@set VERSION 3.81
-@set UPDATED 07 May 2005
-@set UPDATE-MONTH May 2005
-@c ISBN provided by Lisa M. Opus Goldstein <opus@gnu.org>, 5 May 2004
-@set ISBN 1-882114-83-5
-
-@c finalout
-
-@c ISPELL CHECK: done, 10 June 1993 --roland
-@c ISPELL CHECK: done, 2000-06-25 --Martin Buchholz
-
 @c Combine the variable and function indices:
 @syncodeindex vr fn
 @c Combine the program and concept indices:
 @syncodeindex pg cp
+@c FSF publishers: format makebook.texi instead of using this file directly.
+@c ISBN provided by Lisa M. Opus Goldstein <opus@gnu.org>, 5 May 2004
+@set ISBN 1-882114-83-5
+@c %**end of header
+
+@copying
+This file documents the GNU @code{make} utility, which determines
+automatically which pieces of a large program need to be recompiled,
+and issues the commands to recompile them.
+
+This is Edition @value{EDITION}, last updated @value{UPDATED},
+of @cite{The GNU Make Manual}, for GNU @code{make} version @value{VERSION}.
+
+Copyright @copyright{} 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995,
+1996, 1997, 1998, 1999, 2000, 2002, 2003, 2004, 2005, 2006
+Free Software Foundation, Inc.
+
+@quotation
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, with the Front-Cover Texts being ``A GNU Manual,''
+and with the Back-Cover Texts as in (a) below.  A copy of the
+license is included in the section entitled ``GNU Free Documentation
+License.''
+
+(a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
+this GNU Manual, like GNU software.  Copies published by the Free
+Software Foundation raise funds for GNU development.''
+@end quotation
+@end copying
+
+@c finalout
+
+@c ISPELL CHECK: done, 10 June 1993 --roland
+@c ISPELL CHECK: done, 2000-06-25 --Martin Buchholz
+
 
 @dircategory GNU Packages
@@ -30 +55 @@
 * Make: (make).            Remake files automatically.
 @end direntry
-
-@ifnottex
-This file documents the GNU Make utility, which determines
-automatically which pieces of a large program need to be recompiled,
-and issues the commands to recompile them.
-
-This is Edition @value{EDITION}, last updated @value{UPDATED},
-of @cite{The GNU Make Manual}, for @code{make}, Version @value{VERSION}.
-
-Copyright 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1997,
-1998, 1999, 2000, 2002, 2003, 2004, 2005
-Free Software Foundation, Inc.
-
-Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.1 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, with no Front-Cover Texts, and with no Back-Cover
-Texts.  A copy of the license is included in the section entitled
-``GNU Free Documentation License''.
-@end ifnottex
 
 @iftex
@@ -58 +63 @@
 @subtitle A Program for Directing Recompilation
 @subtitle GNU @code{make} Version @value{VERSION}
-@subtitle @value{UPDATE-MONTH}
+@subtitle @value{UPDATED-MONTH}
 @author Richard M. Stallman, Roland McGrath, Paul D. Smith
 @page
 @vskip 0pt plus 1filll
-Copyright @copyright{} 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995,
-1996, 1997, 1998, 1999, 2000, 2002, 2003, 2004 Free Software Foundation, Inc.
+@insertcopying
 @sp 2
 Published by the Free Software Foundation @*
-59 Temple Place -- Suite 330, @*
-Boston, MA 02111-1307 USA @*
+51 Franklin St. -- Fifth Floor @*
+Boston, MA 02110-1301 USA @*
 ISBN @value{ISBN} @*
-
-Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.1 or
-any later version published by the Free Software Foundation; with the
-Invariant Sections being ``GNU General Public License'', the Front-Cover
-Texts being ``A GNU Manual'', and with the Back-Cover Texts being as in
-(a) below.  A copy of the license is included in the section entitled
-``GNU Free Documentation License''.
-
-(a) The FSF's Back-Cover Text is:
-
-@quotation
-      You have freedom to copy and modify this GNU Manual, like GNU
-      software.  Copies published by the Free Software Foundation raise
-      funds for GNU development.
-@end quotation
 @sp 2
 Cover art by Etienne Suvasa.
 @end titlepage
-@page
+
+@summarycontents
+@contents
 
 @ifnottex
 @node Top, Overview, (dir), (dir)
-@top Make
-
-The GNU @code{make} utility automatically determines which pieces of a
-large program need to be recompiled, and issues the commands to
-recompile them.@refill
-
-This edition of the @cite{GNU Make Manual},
-last updated @value{UPDATED},
-documents GNU @code{make} Version @value{VERSION}.@refill
-
-This manual describes @code{make} and contains the following chapters:@refill
+@top GNU @code{make}
+
+@insertcopying
 @end ifnottex
 
@@ -174 +156 @@
 * Phony Targets::               Using a target that is not a real file's name.
 * Force Targets::               You can use a target without commands
-                                  or prerequisites to mark other
-                                  targets as phony.
+                                  or prerequisites to mark other targets
+                                  as phony.
 * Empty Targets::               When only the date matters and the
                                   files are empty.
@@ -215 +197 @@
 Writing the Commands in Rules
 
+* Command Syntax::              Command syntax features and pitfalls.
 * Echoing::                     How to control when commands are echoed.
 * Execution::                   How commands are executed.
@@ -223 +206 @@
 * Sequences::                   Defining canned sequences of commands.
 * Empty Commands::              Defining useful, do-nothing commands.
+
+Command Syntax
+
+* Splitting Lines::             Breaking long command lines for readability.
+* Variables in Commands::       Using @code{make} variables in commands.
+
+Command Execution
+
+* Choosing the Shell::          How @code{make} chooses the shell used
+                                  to run commands.
 
 Recursive Use of @code{make}
@@ -268 +261 @@
 * Text Functions::              General-purpose text manipulation functions.
 * File Name Functions::         Functions for manipulating file names.
+* Conditional Functions::       Functions that implement conditions.
 * Foreach Function::            Repeat some text with controlled variation.
-* If Function::                 Conditionally expand a value.
 * Call Function::               Expand a user-defined function.
 * Value Function::              Return the un-expanded value of a variable.
 * Eval Function::               Evaluate the arguments as makefile syntax.
 * Origin Function::             Find where a variable got its value.
+* Flavor Function::             Find out the flavor of a variable.
 * Shell Function::              Substitute the output of a shell command.
 * Make Control Functions::      Functions that control how make runs.
@@ -301 +295 @@
 * Chained Rules::               How to use a chain of implicit rules.
 * Pattern Rules::               How to define new implicit rules.
-* Last Resort::                 How to defining commands for rules
-                                  which cannot find any.
+* Last Resort::                 How to define commands for rules which
+                                  cannot find any.
 * Suffix Rules::                The old-fashioned style of implicit rule.
 * Implicit Rule Search::        The precise algorithm for applying
@@ -330 +324 @@
 
 * Archive Symbols::             How to update archive symbol directories.
-
-Makefile Conventions
-
-* Makefile Basics::             General Conventions for Makefiles
-* Utilities in Makefiles::      Utilities in Makefiles
-* Command Variables::           Variables for Specifying Commands
-* Directory Variables::         Variables for Installation Directories
-* Standard Targets::            Standard Targets for Users
-* Install Command Categories::  Three categories of commands in the `install'
 
 @end detailmenu
@@ -1100 +1085 @@
 
 @noindent
-@var{filenames} can contain shell file name patterns.
+@var{filenames} can contain shell file name patterns.  If
+@var{filenames} is empty, nothing is included and no error is printed.
 @cindex shell file name pattern (in @code{include})
 @cindex shell wildcards (in @code{include})
@@ -1289 +1275 @@
 @code{.DEFAULT_GOAL} variable allows you to discover the current
 default goal, restart the default goal selection algorithm by clearing
-its value, or to explicitly set the default goal. The following
+its value, or to explicitly set the default goal.  The following
 example illustrates these cases:
 
@@ -1330 +1316 @@
 Note that assigning more than one target name to @code{.DEFAULT_GOAL} is
 illegal and will result in an error.
+
+@vindex MAKE_RESTARTS @r{(number of times @code{make} has restarted)}
+@item MAKE_RESTARTS
+This variable is set only if this instance of @code{make} has
+restarted (@pxref{Remaking Makefiles, , How Makefiles Are Remade}): it
+will contain the number of times this instance has restarted.  Note
+this is not the same as recursion (counted by the @code{MAKELEVEL}
+variable).  You should not set, modify, or export this variable.
 
 @vindex .VARIABLES @r{(list of variables)}
@@ -1357 +1351 @@
 
 @table @samp
+
+@item archives
+Supports @code{ar} (archive) files using special filename syntax.
+@xref{Archives, ,Using @code{make} to Update Archive Files}.
+
+@item check-symlink
+Supports the @code{-L} (@code{--check-symlink-times}) flag.
+@xref{Options Summary, ,Summary of Options}.
+
+@item else-if
+Supports ``else if'' non-nested conditionals.  @xref{Conditional
+Syntax, ,Syntax of Conditionals}.
+
+@item jobserver
+Supports ``job server'' enhanced parallel builds.  @xref{Parallel,
+,Parallel Execution}.
+
+@item second-expansion
+Supports secondary expansion of prerequisite lists.
+
+@item order-only
+Supports order-only prerequisites.  @xref{Prerequisite Types, ,Types
+of Prerequisites}.
+
 @item target-specific
 Supports target-specific and pattern-specific variable assignments.
 @xref{Target-specific, ,Target-specific Variable Values}.
 
-@item order-only
-Supports order-only prerequisites.  @xref{Prerequisite Types, ,Types
-of Prerequisites}.
-
-@item second-expansion
-Supports secondary expansion of prerequisite lists.
-
-@item jobserver
-Supports ``job server'' enhanced parallel builds.  @xref{Parallel,
-,Parallel Execution}.
-
-@item check-symlink
-Supports the @code{-L} (@code{--check-symlink-times}) flag.
-@xref{Options Summary, ,Summary of Options}.
-
 @end table
+
+@vindex .INCLUDE_DIRS @r{(list of include directories)}
+@item .INCLUDE_DIRS
+Expands to a list of directories that @code{make} searches for
+included makefiles (@pxref{Include, , Including Other Makefiles}).
 
 @end table
@@ -1600 +1608 @@
 @cindex expansion, secondary
 
+@findex .SECONDEXPANSION
 In the previous section we learned that GNU @code{make} works in two
 distinct phases: a read-in phase and a target-update phase
-(@pxref{Reading Makefiles, , How @code{make} Reads a Makefile}).
-There is an extra wrinkle that comes in between those two phases,
-right at the end of the read-in phase: at that time, all the
-prerequisites of all of the targets are expanded a @emph{second time}.
-In most circumstances this secondary expansion will have no effect,
-since all variable and function references will have been expanded
-during the initial parsing of the makefiles.  In order to take
-advantage of the secondary expansion phase of the parser, then, it's
-necessary to @emph{escape} the variable or function reference in the
-makefile.  In this case the first expansion merely un-escapes the
-reference but doesn't expand it, and expansion is left to the
-secondary expansion phase.  For example, consider this makefile:
-
-@example
+(@pxref{Reading Makefiles, , How @code{make} Reads a Makefile}).  GNU
+make also has the ability to enable a @emph{second expansion} of the
+prerequisites (only) for some or all targets defined in the makefile.
+In order for this second expansion to occur, the special target
+@code{.SECONDEXPANSION} must be defined before the first prerequisite
+list that makes use of this feature.
+
+If that special target is defined then in between the two phases
+mentioned above, right at the end of the read-in phase, all the
+prerequisites of the targets defined after the special target are
+expanded a @emph{second time}.  In most circumstances this secondary
+expansion will have no effect, since all variable and function
+references will have been expanded during the initial parsing of the
+makefiles.  In order to take advantage of the secondary expansion
+phase of the parser, then, it's necessary to @emph{escape} the
+variable or function reference in the makefile.  In this case the
+first expansion merely un-escapes the reference but doesn't expand it,
+and expansion is left to the secondary expansion phase.  For example,
+consider this makefile:
+
+@example
+.SECONDEXPANSION:
 ONEVAR = onefile
 TWOVAR = twofile
@@ -1639 +1656 @@
 
 @example
+.SECONDEXPANSION:
 AVAR = top
 onefile: $(AVAR)
@@ -1658 +1676 @@
 defer the expansion by escaping the @code{$}.  Also, secondary
 expansion occurs for both explicit and implicit (pattern) rules.
-Knowing this, the possible uses for this feature are almost endless.
-For example:
-
-@example
+Knowing this, the possible uses for this feature increase
+dramatically.  For example:
+
+@example
+.SECONDEXPANSION:
 main_OBJS := main.o try.o test.o
 lib_OBJS := lib.o api.o
@@ -1682 +1701 @@
 lib_SRCS := lib.c api.c
 
+.SECONDEXPANSION:
 main lib: $$(patsubst %.c,%.o,$$($$@@_SRCS))
 @end example
@@ -1708 +1728 @@
 of all prerequisites of rules @emph{that have already appeared} for
 the same target (@code{$$+} with repetitions and @code{$$^}
-without). The following example will help illustrate these behaviors:
-
-@example
+without).  The following example will help illustrate these behaviors:
+
+@example
+.SECONDEXPANSION:
+
 foo: foo.1 bar.1 $$< $$^ $$+    # line #1
 
@@ -1718 +1740 @@
 @end example
 
-For the first line, all three variables (@code{$$<}, @code{$$^}, and
-@code{$$+}) expand to the empty string. For the second line, they will
-have values @code{foo.1}, @code{foo.1 bar.1}, and @code{foo.1 bar.1}
-respectively. For the third they will have values @code{foo.1},
-@code{foo.1 bar.1 foo.2 bar.2}, and @code{foo.1 bar.1 foo.2 bar.2}
-respectively.
+In the first prerequisite list, all three variables (@code{$$<},
+@code{$$^}, and @code{$$+}) expand to the empty string.  In the
+second, they will have values @code{foo.1}, @code{foo.1 bar.1}, and
+@code{foo.1 bar.1} respectively.  In the third they will have values
+@code{foo.1}, @code{foo.1 bar.1 foo.2 bar.2}, and @code{foo.1 bar.1
+foo.2 bar.2} respectively.
 
 Rules undergo secondary expansion in makefile order, except that
@@ -1751 +1773 @@
 
 @example
+.SECONDEXPANSION:
+
 foo: bar
 
@@ -1769 +1793 @@
 
 @example
+.SECONDEXPANSION:
+
 /tmp/foo.o:
 
@@ -1816 +1842 @@
 * Phony Targets::               Using a target that is not a real file's name.
 * Force Targets::               You can use a target without commands
-                                  or prerequisites to mark other
-                                  targets as phony.
+                                  or prerequisites to mark other targets
+                                  as phony.
 * Empty Targets::               When only the date matters and the
                                   files are empty.
@@ -1901 +1927 @@
 appear on the line after the prerequisites, with a tab character, or may
 appear on the same line, with a semicolon.  Either way, the effect is the
-same.  @xref{Commands, ,Writing the Commands in Rules}.
+same.  There are other differences in the syntax of command lines.
+@xref{Commands, ,Writing the Commands in Rules}.
 
 @cindex dollar sign (@code{$}), in rules
 @cindex @code{$}, in rules
-@cindex rule, and @code{$}
-Because dollar signs are used to start variable references, if you really
-want a dollar sign in a rule you must write two of them, @samp{$$}
-(@pxref{Using Variables, ,How to Use Variables}).  In prerequisite
-lists you must actually write @emph{four} dollar signs (@samp{$$$$}),
-due to secondary expansion (@pxref{Secondary Expansion}).
-You may split a long line by inserting a backslash
-followed by a newline, but this is not required, as @code{make} places no
-limit on the length of a line in a makefile.
+@cindex rules, and @code{$}
+Because dollar signs are used to start @code{make} variable
+references, if you really want a dollar sign in a target or
+prerequisite you must write two of them, @samp{$$} (@pxref{Using
+Variables, ,How to Use Variables}).  If you have enabled secondary
+expansion (@pxref{Secondary Expansion}) and you want a literal dollar
+sign in the prerequisites lise, you must actually write @emph{four}
+dollar signs (@samp{$$$$}).
+
+You may split a long line by inserting a backslash followed by a
+newline, but this is not required, as @code{make} places no limit on
+the length of a line in a makefile.
 
 A rule tells @code{make} two things: when the targets are out of date,
@@ -2004 +2034 @@
 @var{HOME}.@refill
 
-Wildcard expansion happens automatically in targets, in prerequisites,
-and in commands (where the shell does the expansion).  In other
-contexts, wildcard expansion happens only if you request it explicitly
-with the @code{wildcard} function.
+Wildcard expansion is performed by @code{make} automatically in
+targets and in prerequisites.  In commands the shell is responsible
+for wildcard expansion.  In other contexts, wildcard expansion happens
+only if you request it explicitly with the @code{wildcard} function.
 
 The special significance of a wildcard character can be turned off by
@@ -2553 +2583 @@
 word in the list will be used.
 
-The default value for @code{.LIBPATTERNS} is ``@samp{lib%.so lib%.a}'',
+The default value for @code{.LIBPATTERNS} is @samp{lib%.so lib%.a},
 which provides the default behavior described above.
 
@@ -2644 +2674 @@
 it will do so even if @code{make} is invoked with the @code{-k} option,
 which is unfortunate.  Second, and perhaps more importantly, you cannot
-take advantage of the parallel build capabilities of make using this
-method, since there is only one rule.
+take advantage of @code{make}'s ability to build targets in parallel
+(@pxref{Parallel, ,Parallel Execution}), since there is only one rule.
 
 By declaring the subdirectories as phony targets (you must do this as
@@ -2867 +2897 @@
 as secondary (i.e., no target is removed because it is considered
 intermediate).
+
+@findex .SECONDEXPANSION
+@item .SECONDEXPANSION
+
+If @code{.SECONDEXPANSION} is mentioned as a target anywhere in the
+makefile, then all prerequisite lists defined @emph{after} it appears
+will be expanded a second time after all makefiles have been read in.
+@xref{Secondary Expansion, ,Secondary Expansion}.
+
+The prerequisites of the special target @code{.SUFFIXES} are the list
+of suffixes to be used in checking for suffix rules.
+@xref{Suffix Rules, , Old-Fashioned Suffix Rules}.
 
 @findex .DELETE_ON_ERROR
@@ -3376 +3418 @@
 @group
 %.d: %.c
-        @set -e; rm -f $@@; \
+        @@set -e; rm -f $@@; \
          $(CC) -M $(CPPFLAGS) $< > $@@.$$$$; \
          sed 's,\($*\)\.o[ :]*,\1.o $@@ : ,g' < $@@.$$$$ > $@@; \
@@ -3449 +3491 @@
 @cindex writing rule commands
 
-The commands of a rule consist of shell command lines to be executed one
-by one.  Each command line must start with a tab, except that the first
-command line may be attached to the target-and-prerequisites line with a
-semicolon in between.  Blank lines and lines of just comments may appear
-among the command lines; they are ignored.  (But beware, an apparently
-``blank'' line that begins with a tab is @emph{not} blank!  It is an
-empty command; @pxref{Empty Commands}.)
+The commands of a rule consist of one or more shell command lines to
+be executed, one at a time, in the order they appear.  Typically, the
+result of executing these commands is that the target of the rule is
+brought up to date.
 
 Users use many different shell programs, but commands in makefiles are
@@ -3461 +3500 @@
 otherwise.  @xref{Execution, ,Command Execution}.
 
-@cindex comments, in commands
-@cindex commands, comments in
-@cindex @code{#} (comments), in commands
-The shell that is in use determines whether comments can be written on
-command lines, and what syntax they use.  When the shell is
-@file{/bin/sh}, a @samp{#} starts a comment that extends to the end of
-the line.  The @samp{#} does not have to be at the beginning of a line.
-Text on a line before a @samp{#} is not part of the comment.
-
 @menu
+* Command Syntax::              Command syntax features and pitfalls.
 * Echoing::                     How to control when commands are echoed.
 * Execution::                   How commands are executed.
@@ -3481 +3512 @@
 @end menu
 
-@node Echoing, Execution, Commands, Commands
+@node Command Syntax, Echoing, Commands, Commands
+@section Command Syntax
+@cindex command syntax
+@cindex syntax of commands
+
+Makefiles have the unusual property that there are really two distinct
+syntaxes in one file.  Most of the makefile uses @code{make} syntax
+(@pxref{Makefiles, ,Writing Makefiles}).  However, commands are meant to be
+interpreted by the shell and so they are written using shell syntax.
+The @code{make} program does not try to understand shell syntax: it
+performs only a very few specific translations on the content of the
+command before handing it to the shell.
+
+Each command line must start with a tab, except that the first command
+line may be attached to the target-and-prerequisites line with a
+semicolon in between.  @emph{Any} line in the makefile that begins
+with a tab and appears in a ``rule context'' (that is, after a rule
+has been started until another rule or variable definition) will be
+considered a command line for that rule.  Blank lines and lines of
+just comments may appear among the command lines; they are ignored.
+
+Some consequences of these rules include:
+
+@itemize @bullet
+@item
+A blank line that begins with a tab is not blank: it's an empty
+command (@pxref{Empty Commands}).
+
+@cindex comments, in commands
+@cindex commands, comments in
+@cindex @code{#} (comments), in commands
+@item
+A comment in a command line is not a @code{make} comment; it will be
+passed to the shell as-is.  Whether the shell treats it as a comment
+or not depends on your shell.
+
+@item
+A variable definition in a ``rule context'' which is indented by a tab
+as the first character on the line, will be considered a command line,
+not a @code{make} variable definition, and passed to the shell.
+
+@item
+A conditional expression (@code{ifdef}, @code{ifeq},
+etc. @pxref{Conditional Syntax, ,Syntax of Conditionals}) in a ``rule
+context'' which is indented by a tab as the first character on the
+line, will be considered a command line and be passed to the shell.
+
+@end itemize
+
+@menu
+* Splitting Lines::             Breaking long command lines for readability.
+* Variables in Commands::       Using @code{make} variables in commands.
+@end menu
+
+@node Splitting Lines, Variables in Commands, Command Syntax, Command Syntax
+@subsection Splitting Command Lines
+@cindex commands, splitting
+@cindex splitting commands
+@cindex commands, backslash (@code{\}) in
+@cindex commands, quoting newlines in
+@cindex backslash (@code{\}), in commands
+@cindex @code{\} (backslash), in commands
+@cindex quoting newline, in commands
+@cindex newline, quoting, in commands
+
+One of the few ways in which @code{make} does interpret command lines
+is checking for a backslash just before the newline.  As in normal
+makefile syntax, a single command can be split into multiple lines in
+the makefile by placing a backslash before each newline.  A sequence
+of lines like this is considered a single command, and one instance of
+the shell will be invoked to run it.
+
+However, in contrast to how they are treated in other places in a
+makefile, backslash-newline pairs are @emph{not} removed from the
+command.  Both the backslash and the newline characters are preserved
+and passed to the shell.  How the backslash-newline is interpreted
+depends on your shell.  If the first character of the next line
+after the backslash-newline is a tab, then that tab (and only that
+tab) is removed.  Whitespace is never added to the command.
+
+For example, this makefile:
+
+@example
+@group
+all :
+        @@echo no\
+space
+        @@echo no\
+        space
+        @@echo one \
+        space
+        @@echo one\
+         space
+@end group
+@end example
+
+@noindent
+consists of four separate shell commands where the output is:
+
+@example
+@group
+nospace
+nospace
+one space
+one space
+@end group
+@end example
+
+As a more complex example, this makefile:
+
+@example
+@group
+all : ; @@echo 'hello \
+        world' ; echo "hello \
+    world"
+@end group
+@end example
+
+@noindent
+will run one shell with a command script of:
+
+@example
+@group
+echo 'hello \
+world' ; echo "hello \
+    world"
+@end group
+@end example
+
+@noindent
+which, according to shell quoting rules, will yield the following output:
+
+@example
+@group
+hello \
+world
+hello     world
+@end group
+@end example
+
+@noindent
+Notice how the backslash/newline pair was removed inside the string quoted
+with double quotes (@code{"..."}), but not from the string quoted with single
+quotes (@code{'...'}).  This is the way the default shell (@file{/bin/sh})
+handles backslash/newline pairs.  If you specify a different shell in your
+makefiles it may treat them differently.
+
+Sometimes you want to split a long line inside of single quotes, but
+you don't want the backslash-newline to appear in the quoted content.
+This is often the case when passing scripts to languages such as Perl,
+where extraneous backslashes inside the script can change its meaning
+or even be a syntax error.  One simple way of handling this is to
+place the quoted string, or even the entire command, into a
+@code{make} variable then use the variable in the command.  In this
+situation the newline quoting rules for makefiles will be used, and
+the backslash-newline will be removed.  If we rewrite our example
+above using this method:
+
+@example
+@group
+HELLO = 'hello \
+world'
+
+all : ; @@echo $(HELLO)
+@end group
+@end example
+
+@noindent
+we will get output like this:
+
+@example
+@group
+hello world
+@end group
+@end example
+
+If you like, you can also use target-specific variables
+(@pxref{Target-specific, ,Target-specific Variable Values}) to obtain
+a tighter correspondence between the variable and the command that
+uses it.
+
+@node Variables in Commands,  , Splitting Lines, Command Syntax
+@subsection Using Variables in Commands
+@cindex variable references in commands
+@cindex commands, using variables in
+
+The other way in which @code{make} processes commands is by expanding
+any variable references in them (@pxref{Reference,Basics of Variable
+References}).  This occurs after make has finished reading all the
+makefiles and the target is determined to be out of date; so, the
+commands for targets which are not rebuilt are never expanded.
+
+Variable and function references in commands have identical syntax and
+semantics to references elsewhere in the makefile.  They also have the
+same quoting rules: if you want a dollar sign to appear in your
+command, you must double it (@samp{$$}).  For shells like the default
+shell, that use dollar signs to introduce variables, it's important to
+keep clear in your mind whether the variable you want to reference is
+a @code{make} variable (use a single dollar sign) or a shell variable
+(use two dollar signs).  For example:
+
+@example
+@group
+LIST = one two three
+all:
+        for i in $(LIST); do \
+            echo $$i; \
+        done
+@end group
+@end example
+
+@noindent
+results in the following command being passed to the shell:
+
+@example
+@group
+for i in one two three; do \
+    echo $i; \
+done
+@end group
+@end example
+
+@noindent
+which generates the expected result:
+
+@example
+@group
+one
+two
+three
+@end group
+@end example
+
+@node Echoing, Execution, Command Syntax, Commands
 @section Command Echoing
 @cindex echoing of commands
@@ -3530 +3794 @@
 @cindex execution, of commands
 @cindex shell command, execution
-@vindex SHELL @r{(command execution)}
-
-When it is time to execute commands to update a target, they are executed
-by making a new subshell for each line.  (In practice, @code{make} may
-take shortcuts that do not affect the results.)
+@vindex @code{SHELL} @r{(command execution)}
+
+When it is time to execute commands to update a target, they are
+executed by invoking a new subshell for each command line.  (In
+practice, @code{make} may take shortcuts that do not affect the
+results.)
 
 @cindex @code{cd} (shell command)
-@strong{Please note:} this implies that shell commands such as @code{cd}
-that set variables local to each process will not affect the following
-command lines. @footnote{On MS-DOS, the value of current working
-directory is @strong{global}, so changing it @emph{will} affect the
-following command lines on those systems.}  If you want to use @code{cd}
-to affect the next command, put the two on a single line with a
-semicolon between them.  Then @code{make} will consider them a single
-command and pass them, together, to a shell which will execute them in
-sequence.  For example:
+@cindex shell variables, setting in commands
+@cindex commands setting shell variables
+@strong{Please note:} this implies that setting shell variables and
+invoking shell commands such as @code{cd} that set a context local to
+each process will not affect the following command lines.@footnote{On
+MS-DOS, the value of current working directory is @strong{global}, so
+changing it @emph{will} affect the following command lines on those
+systems.}  If you want to use @code{cd} to affect the next statement,
+put both statements in a single command line.  Then @code{make} will
+invoke one shell to run the entire line, and the shell will execute
+the statements in sequence.  For example:
 
 @example
 foo : bar/lose
-        cd bar; gobble lose > ../foo
-@end example
-
-@cindex commands, backslash (@code{\}) in
-@cindex commands, quoting newlines in
-@cindex backslash (@code{\}), in commands
-@cindex @code{\} (backslash), in commands
-@cindex quoting newline, in commands
-@cindex newline, quoting, in commands
-If you would like to split a single shell command into multiple lines of
-text, you must use a backslash at the end of all but the last subline.
-Such a sequence of lines is combined into a single line, by deleting the
-backslash-newline sequences, before passing it to the shell.  Thus, the
-following is equivalent to the preceding example:
-
-@example
-@group
-foo : bar/lose
-        cd bar;  \
-        gobble lose > ../foo
-@end group
-@end example
+        cd $(@@D) && gobble $(@@F) > ../$@@
+@end example
+
+@noindent
+Here we use the shell AND operator (@code{&&}) so that if the
+@code{cd} command fails, the script will fail without trying to invoke
+the @code{gobble} command in the wrong directory, which could cause
+problems (in this case it would certainly cause @file{../foo} to be
+truncated, at least).
+
+@menu
+* Choosing the Shell::          How @code{make} chooses the shell used
+                                  to run commands.
+@end menu
+
+@node Choosing the Shell,  , Execution, Execution
+@subsection Choosing the Shell
+@cindex shell, choosing the
+@cindex @code{SHELL}, value of
 
 @vindex SHELL
 The program used as the shell is taken from the variable @code{SHELL}.
-By default, the program @file{/bin/sh} is used.
+If this variable is not set in your makefile, the program
+@file{/bin/sh} is used as the shell.
+
+@cindex environment, @code{SHELL} in
+Unlike most variables, the variable @code{SHELL} is never set from the
+environment.  This is because the @code{SHELL} environment variable is
+used to specify your personal choice of shell program for interactive
+use.  It would be very bad for personal choices like this to affect the
+functioning of makefiles.  @xref{Environment, ,Variables from the
+Environment}.
+
+Furthermore, when you do set @code{SHELL} in your makefile that value
+is @emph{not} exported in the environment to commands that @code{make}
+invokes.  Instead, the value inherited from the user's environment, if
+any, is exported.  You can override this behavior by explicitly
+exporting @code{SHELL} (@pxref{Variables/Recursion, ,Communicating
+Variables to a Sub-@code{make}}), forcing it to be passed in the
+environment to commands.
+
+@vindex @code{MAKESHELL} @r{(MS-DOS alternative to @code{SHELL})}
+However, on MS-DOS and MS-Windows the value of @code{SHELL} in the
+environment @strong{is} used, since on those systems most users do not
+set this variable, and therefore it is most likely set specifically to
+be used by @code{make}.  On MS-DOS, if the setting of @code{SHELL} is
+not suitable for @code{make}, you can set the variable
+@code{MAKESHELL} to the shell that @code{make} should use; if set it
+will be used as the shell instead of the value of @code{SHELL}.
+
+@subsubheading Choosing a Shell in DOS and Windows
+@cindex shell, in DOS and Windows
+@cindex DOS, choosing a shell in
+@cindex Windows, choosing a shell in
+
+Choosing a shell in MS-DOS and MS-Windows is much more complex than on
+other systems.
 
 @vindex COMSPEC
@@ -3628 +3926 @@
 
 The effect of the above DOS-specific processing is that a Makefile that
-says @samp{SHELL = /bin/sh} (as many Unix makefiles do), will work
-on MS-DOS unaltered if you have e.g. @file{sh.exe} installed in some
+contains @samp{SHELL = /bin/sh} (as many Unix makefiles do), will work
+on MS-DOS unaltered if you have e.g.@: @file{sh.exe} installed in some
 directory along your @code{PATH}.
-
-@cindex environment, @code{SHELL} in
-@vindex MAKESHELL @r{(MS-DOS alternative to @code{SHELL})}
-Unlike most variables, the variable @code{SHELL} is never set from the
-environment.  This is because the @code{SHELL} environment variable is
-used to specify your personal choice of shell program for interactive
-use.  It would be very bad for personal choices like this to affect the
-functioning of makefiles.  @xref{Environment, ,Variables from the
-Environment}.  However, on MS-DOS and MS-Windows the value of
-@code{SHELL} in the environment @strong{is} used, since on those systems
-most users do not set this variable, and therefore it is most likely set
-specifically to be used by @code{make}.  On MS-DOS, if the setting of
-@code{SHELL} is not suitable for @code{make}, you can set the variable
-@code{MAKESHELL} to the shell that @code{make} should use; this will
-override the value of @code{SHELL}.
 
 @node Parallel, Errors, Execution, Commands
@@ -4015 +4298 @@
 environment is passed to the sub-@code{make}.  You can force
 @code{make} to export its value for @code{SHELL} by using the
-@code{export} directive, described below.
+@code{export} directive, described below.  @xref{Choosing the Shell}.
 
 The special variable @code{MAKEFLAGS} is always exported (unless you
@@ -4712 +4995 @@
 @group
 ifeq (0,$@{MAKELEVEL@})
-cur-dir   := $(shell pwd)
 whoami    := $(shell whoami)
 host-type := $(shell arch)
@@ -4727 +5009 @@
 @group
 $@{subdirs@}:
-      $@{MAKE@} cur-dir=$@{cur-dir@}/$@@ -C $@@ all
+        $@{MAKE@} -C $@@ all
 @end group
 @end example
@@ -5197 +5479 @@
 simply-expanded definition, and expands the new text before appending it
 to the old value just as @samp{:=} does
-(@pxref{Setting, ,Setting Variables}, for a full explanation of @samp{:=}).
+(see @ref{Setting, ,Setting Variables}, for a full explanation of @samp{:=}).
 In fact,
 
@@ -5438 +5720 @@
 When @code{make} runs a command script, variables defined in the
 makefile are placed into the environment of that command.  This allows
-you to pass values to sub-@code{make} invocations. (@pxref{Recursion,
+you to pass values to sub-@code{make} invocations (@pxref{Recursion,
 ,Recursive Use of @code{make}}).  By default, only variables that came
 from the environment or the command line are passed to recursive
@@ -5452 +5734 @@
 
 @cindex SHELL, import from environment
-Such problems would be especially likely with the variable @code{SHELL},
-which is normally present in the environment to specify the user's choice
-of interactive shell.  It would be very undesirable for this choice to
-affect @code{make}.  So @code{make} ignores the environment value of
-@code{SHELL} (except on MS-DOS and MS-Windows, where @code{SHELL} is
-usually not set.  @xref{Execution, ,Special handling of SHELL on
-MS-DOS}.)@refill
-
-@cindex SHELL, export to environment
-The @code{SHELL} variable is special in another way: just as the value
-of the @code{make} variable @code{SHELL} is not taken from the
-environment, so also it is not placed into the environment of commands
-that @code{make} invokes.  Instead, the value of @code{SHELL} from the
-invoking environment is provided to the command.  You can use
-@code{export SHELL} to force the value of the @code{make} variable
-@code{SHELL} to be placed in the environment of commands.
+Such problems would be especially likely with the variable
+@code{SHELL}, which is normally present in the environment to specify
+the user's choice of interactive shell.  It would be very undesirable
+for this choice to affect @code{make}; so, @code{make} handles the
+@code{SHELL} environment variable in a special way; see @ref{Choosing
+the Shell}.@refill
 
 @node Target-specific, Pattern-specific, Environment, Using Variables
@@ -5515 +5787 @@
 will be in effect.  Note that this variable is actually distinct from
 any ``global'' value: the two variables do not have to have the same
-flavor (recursive vs. static).
+flavor (recursive vs.@: static).
 
 Target-specific variables have the same priority as any other makefile
@@ -5526 +5798 @@
 you define a target-specific variable that variable value is also in
 effect for all prerequisites of this target, and all their
-prerequisites, etc. (unless those prerequisites override that variable
+prerequisites, etc.@: (unless those prerequisites override that variable
 with their own target-specific variable value).  So, for example, a
 statement like this:
@@ -5925 +6197 @@
 * Text Functions::              General-purpose text manipulation functions.
 * File Name Functions::         Functions for manipulating file names.
+* Conditional Functions::       Functions that implement conditions.
 * Foreach Function::            Repeat some text with controlled variation.
-* If Function::                 Conditionally expand a value.
 * Call Function::               Expand a user-defined function.
 * Value Function::              Return the un-expanded value of a variable.
 * Eval Function::               Evaluate the arguments as makefile syntax.
 * Origin Function::             Find where a variable got its value.
+* Flavor Function::             Find out the flavor of a variable.
 * Shell Function::              Substitute the output of a shell command.
 * Make Control Functions::      Functions that control how make runs.
@@ -6345 +6618 @@
 Directive, , The @code{override} Directive}).
 
-@node File Name Functions, Foreach Function, Text Functions, Functions
+@node File Name Functions, Conditional Functions, Text Functions, Functions
 @section Functions for File Names
 @cindex functions, for file names
@@ -6505 +6778 @@
 For each file name in @var{names} return the canonical absolute name.
 A canonical name does not contain any @code{.} or @code{..} components,
-nor any repeated path separators (@code{/}) or symlinks. In case of a
-failure the empty string is returned. Consult the @code{realpath(3)}
+nor any repeated path separators (@code{/}) or symlinks.  In case of a
+failure the empty string is returned.  Consult the @code{realpath(3)}
 documentation for a list of possible failure causes.
 
@@ -6515 +6788 @@
 For each file name in @var{names} return an absolute name that does
 not contain any @code{.} or @code{..} components, nor any repeated path
-separators (@code{/}). Note that in contrast to @code{realpath}
+separators (@code{/}).  Note that, in contrast to @code{realpath}
 function, @code{abspath} does not resolve symlinks and does not require
-the file names to refer to an existing file or directory. Use the
+the file names to refer to an existing file or directory.  Use the
 @code{wildcard} function to test for existence.
 @end table
 
-@node Foreach Function, If Function, File Name Functions, Functions
+@node Conditional Functions, Foreach Function, File Name Functions, Functions
+@section Functions for Conditionals
+@findex if
+@cindex conditional expansion
+There are three functions that provide conditional expansion.  A key
+aspect of these functions is that not all of the arguments are
+expanded initially.  Only those arguments which need to be expanded,
+will be expanded.
+
+@table @code
+@item $(if @var{condition},@var{then-part}[,@var{else-part}])
+@findex if
+The @code{if} function provides support for conditional expansion in a
+functional context (as opposed to the GNU @code{make} makefile
+conditionals such as @code{ifeq} (@pxref{Conditional Syntax, ,Syntax of
+Conditionals}).
+
+The first argument, @var{condition}, first has all preceding and
+trailing whitespace stripped, then is expanded.  If it expands to any
+non-empty string, then the condition is considered to be true.  If it
+expands to an empty string, the condition is considered to be false.
+
+If the condition is true then the second argument, @var{then-part}, is
+evaluated and this is used as the result of the evaluation of the entire
+@code{if} function.
+
+If the condition is false then the third argument, @var{else-part}, is
+evaluated and this is the result of the @code{if} function.  If there is
+no third argument, the @code{if} function evaluates to nothing (the
+empty string).
+
+Note that only one of the @var{then-part} or the @var{else-part} will be
+evaluated, never both.  Thus, either can contain side-effects (such as
+@code{shell} function calls, etc.)
+
+@item $(or @var{condition1}[,@var{condition2}[,@var{condition3}@dots{}]])
+@findex or
+The @code{or} function provides a ``short-circuiting'' OR operation.
+Each argument is expanded, in order.  If an argument expands to a
+non-empty string the processing stops and the result of the expansion
+is that string.  If, after all arguments are expanded, all of them are
+false (empty), then the result of the expansion is the empty string.
+
+@item $(and @var{condition1}[,@var{condition2}[,@var{condition3}@dots{}]])
+@findex and
+The @code{and} function provides a ``short-circuiting'' AND operation.
+Each argument is expanded, in order.  If an argument expands to an
+empty string the processing stops and the result of the expansion is
+the empty string.  If all arguments expand to a non-empty string then
+the result of the expansion is the expansion of the last argument.
+
+@end table
+
+@node Foreach Function, Call Function, Conditional Functions, Functions
 @section The @code{foreach} Function
 @findex foreach
@@ -6609 +6935 @@
 no?), but it is more likely to be a mistake.
 
-@node If Function, Call Function, Foreach Function, Functions
-@section The @code{if} Function
-@findex if
-@cindex conditional expansion
-
-The @code{if} function provides support for conditional expansion in a
-functional context (as opposed to the GNU @code{make} makefile
-conditionals such as @code{ifeq} (@pxref{Conditional Syntax, ,Syntax of
-Conditionals}).
-
-An @code{if} function call can contain either two or three arguments:
-
-@example
-$(if @var{condition},@var{then-part}[,@var{else-part}])
-@end example
-
-The first argument, @var{condition}, first has all preceding and
-trailing whitespace stripped, then is expanded.  If it expands to any
-non-empty string, then the condition is considered to be true.  If it
-expands to an empty string, the condition is considered to be false.
-
-If the condition is true then the second argument, @var{then-part}, is
-evaluated and this is used as the result of the evaluation of the entire
-@code{if} function.
-
-If the condition is false then the third argument, @var{else-part}, is
-evaluated and this is the result of the @code{if} function.  If there is
-no third argument, the @code{if} function evaluates to nothing (the
-empty string).
-
-Note that only one of the @var{then-part} or the @var{else-part} will be
-evaluated, never both.  Thus, either can contain side-effects (such as
-@code{shell} function calls, etc.)
-
-@node Call Function, Value Function, If Function, Functions
+@node Call Function, Value Function, Foreach Function, Functions
 @section The @code{call} Function
 @findex call
@@ -6713 +7005 @@
 
 The @code{call} function can be nested.  Each recursive invocation gets
-its own local values for @code{$(1)}, etc. that mask the values of
+its own local values for @code{$(1)}, etc.@: that mask the values of
 higher-level @code{call}.  For example, here is an implementation of a
 @dfn{map} function:
@@ -6850 +7142 @@
 @end example
 
-@node Origin Function, Shell Function, Eval Function, Functions
+@node Origin Function, Flavor Function, Eval Function, Functions
 @section The @code{origin} Function
 @findex origin
@@ -6959 +7251 @@
 @xref{Text Functions, , Functions for String Substitution and Analysis}.
 
-@node Shell Function, Make Control Functions, Origin Function, Functions
+@node Flavor Function, Shell Function, Origin Function, Functions
+@section The @code{flavor} Function
+@findex flavor
+@cindex variables, flavor of
+@cindex flavor of variable
+
+The @code{flavor} function is unlike most other functions (and like
+@code{origin} function) in that it does not operate on the values of
+variables; it tells you something @emph{about} a variable.
+Specifically, it tells you the flavor of a variable (@pxref{Flavors,
+,The Two Flavors of Variables}).
+
+The syntax of the @code{flavor} function is:
+
+@example
+$(flavor @var{variable})
+@end example
+
+Note that @var{variable} is the @emph{name} of a variable to inquire about;
+not a @emph{reference} to that variable.  Therefore you would not normally
+use a @samp{$} or parentheses when writing it.  (You can, however, use a
+variable reference in the name if you want the name not to be a constant.)
+
+The result of this function is a string that identifies the flavor of the
+variable @var{variable}:
+
+@table @samp
+@item undefined
+
+if @var{variable} was never defined.
+
+@item recursive
+
+if @var{variable} is a recursively expanded variable.
+
+@item simple
+
+if @var{variable} is a simply expanded variable.
+
+@end table
+
+
+@node Shell Function, Make Control Functions, Flavor Function, Functions
 @section The @code{shell} Function
 @findex shell
@@ -6984 +7318 @@
 spawning a new shell, you should carefully consider the performance
 implications of using the @code{shell} function within recursively
-expanded variables vs. simply expanded variables (@pxref{Flavors, ,The
+expanded variables vs.@: simply expanded variables (@pxref{Flavors, ,The
 Two Flavors of Variables}).
 
@@ -7084 +7418 @@
 things and many others.
 
+@cindex exit status of make
 The exit status of @code{make} is always one of three values:
 @table @code
@@ -7550 +7885 @@
 Consider all targets out-of-date.  GNU @code{make} proceeds to
 consider targets and their prerequisites using the normal algorithms;
-however, all these targets are remade, regardless of the status of
-their prerequisites.
+however, all targets so considered are always remade regardless of the
+status of their prerequisites.  To avoid infinite recursion, if
+@code{MAKE_RESTARTS} (@pxref{Special Variables, , Other Special
+Variables}) is set to a number greater than 0 this option is disabled
+when considering whether to remake makefiles (@pxref{Remaking
+Makefiles, , How Makefiles Are Remade}).
 
 @item -C @var{dir}
@@ -7907 +8246 @@
 * Pattern Rules::               How to define new implicit rules.
 * Last Resort::                 How to define commands for rules which
-                                cannot find any.
+                                  cannot find any.
 * Suffix Rules::                The old-fashioned style of implicit rule.
 * Implicit Rule Search::        The precise algorithm for applying
@@ -8002 +8341 @@
 @samp{--no-builtin-rules} option cancels all predefined rules.
 
+This manual only documents the default rules available on POSIX-based
+operating systems.  Other operating systems, such as VMS, Windows,
+OS/2, etc. may have different sets of default rules.  To see the full
+list of default rules and variables available in your version of GNU
+@code{make}, run @samp{make -p} in a directory with no makefile.
+
 Not all of these rules will always be defined, even when the @samp{-r}
 option is not given.  Many of the predefined implicit rules are
@@ -8008 +8353 @@
 the special target @code{.SUFFIXES}).  The default suffix list is:
 @code{.out}, @code{.a}, @code{.ln}, @code{.o}, @code{.c}, @code{.cc},
-@code{.C}, @code{.p}, @code{.f}, @code{.F}, @code{.r}, @code{.y},
+@code{.C}, @code{.cpp}, @code{.p}, @code{.f}, @code{.F}, @code{.r}, @code{.y},
 @code{.l}, @code{.s}, @code{.S}, @code{.mod}, @code{.sym}, @code{.def},
 @code{.h}, @code{.info}, @code{.dvi}, @code{.tex}, @code{.texinfo},
@@ -8033 +8378 @@
 @cindex C++, rule to compile
 @pindex g++
+@pindex .cc
+@pindex .cpp
 @pindex .C
-@pindex .cc
-@file{@var{n}.o} is made automatically from @file{@var{n}.cc} or
-@file{@var{n}.C} with a command of the form @samp{$(CXX) -c $(CPPFLAGS)
-$(CXXFLAGS)}.  We encourage you to use the suffix @samp{.cc} for C++
-source files instead of @samp{.C}.@refill
+@file{@var{n}.o} is made automatically from @file{@var{n}.cc},
+@file{@var{n}.cpp}, or @file{@var{n}.C} with a command of the form
+@samp{$(CXX) -c $(CPPFLAGS) $(CXXFLAGS)}.  We encourage you to use the
+suffix @samp{.cc} for C++ source files instead of @samp{.C}.@refill
 
 @item Compiling Pascal programs
@@ -8299 +8645 @@
 
 The commands in built-in implicit rules make liberal use of certain
-predefined variables.  You can alter these variables in the makefile,
-with arguments to @code{make}, or in the environment to alter how the
-implicit rules work without redefining the rules themselves.  You can
-cancel all variables used by implicit rules with the @samp{-R} or
-@samp{--no-builtin-variables} option.
+predefined variables.  You can alter the values of these variables in
+the makefile, with arguments to @code{make}, or in the environment to
+alter how the implicit rules work without redefining the rules
+themselves.  You can cancel all variables used by implicit rules with
+the @samp{-R} or @samp{--no-builtin-variables} option.
 
 For example, the command used to compile a C source file actually says
@@ -8322 +8668 @@
 with spaces.
 
-Here is a table of variables used as names of programs in built-in rules:
+The following tables describe of some of the more commonly-used predefined
+variables.  This list is not exhaustive, and the default values shown here may
+not be what are selected by @code{make} for your environment.  To see the
+complete list of predefined variables for your instance of GNU @code{make} you
+can run @samp{make -p} in a directory with no makefiles.
+
+Here is a table of some of the more common variables used as names of
+programs in built-in rules:
+makefiles.
 
 @table @code
@@ -8332 +8686 @@
 @item AS
 @vindex AS
-Program for doing assembly; default @samp{as}.
+Program for compiling assembly files; default @samp{as}.
 @pindex as
 
@@ -8338 +8692 @@
 @vindex CC
 Program for compiling C programs; default @samp{cc}.
+@pindex cc
+
+@item CO
+@vindex CO
+Program for checking out files from RCS; default @samp{co}.
 @pindex cc
 
@@ -8368 +8727 @@
 @item LEX
 @vindex LEX
-Program to use to turn Lex grammars into C programs or Ratfor programs;
-default @samp{lex}.
+Program to use to turn Lex grammars into source code; default @samp{lex}.
 @pindex lex
+
+@item YACC
+@vindex YACC
+Program to use to turn Yacc grammars into source code; default @samp{yacc}.
+@pindex yacc
+
+@item LINT
+@vindex LINT
+Program to use to run lint on source code; default @samp{lint}.
+@pindex lint
+
+@item M2C
+@vindex M2C
+Program to use to compile Modula-2 source code; default @samp{m2c}.
+@pindex m2c
 
 @item PC
@@ -8376 +8749 @@
 Program for compiling Pascal programs; default @samp{pc}.
 @pindex pc
-
-@item YACC
-@vindex YACC
-Program to use to turn Yacc grammars into C programs; default @samp{yacc}.
-@pindex yacc
-
-@item YACCR
-@vindex YACCR
-Program to use to turn Yacc grammars into Ratfor
-programs; default @samp{yacc -r}.
 
 @item MAKEINFO
@@ -8472 +8835 @@
 @item LDFLAGS
 @vindex LDFLAGS
-Extra flags to give to compilers when they are
-supposed to invoke the linker, @samp{ld}.
+Extra flags to give to compilers when they are supposed to invoke the linker,
+@samp{ld}.
 
 @item LFLAGS
@@ -8479 +8842 @@
 Extra flags to give to Lex.
 
+@item YFLAGS
+@vindex YFLAGS
+Extra flags to give to Yacc.
+
 @item PFLAGS
 @vindex PFLAGS
@@ -8487 +8854 @@
 Extra flags to give to the Fortran compiler for Ratfor programs.
 
-@item YFLAGS
-@vindex YFLAGS
-Extra flags to give to Yacc.
+@item LINTFLAGS
+@vindex LINTFLAGS
+Extra flags to give to lint.
 @end table
 
@@ -8629 +8996 @@
 
 @samp{%} in a prerequisite of a pattern rule stands for the same stem
-that was matched by the @samp{%} in the target.  In order for
-the pattern rule to apply, its target pattern must match the file name
-under consideration, and its prerequisite patterns must name files that
-exist or can be made.  These files become prerequisites of the target.
+that was matched by the @samp{%} in the target.  In order for the
+pattern rule to apply, its target pattern must match the file name
+under consideration and all of its prerequisites (after pattern
+substitution) must name files that exist or can be made.  These files
+become prerequisites of the target.
 @cindex prerequisite pattern, implicit
 
@@ -8982 +9350 @@
 names, along with the slash that ends them, are added on to the
 prerequisite file names generated from the pattern rule's prerequisite
-patterns and the file name. The directories are ignored only for the
+patterns and the file name.  The directories are ignored only for the
 purpose of finding an implicit rule to use, not in the application of
 that rule.  Thus, @samp{e%t} matches the file name @file{src/eat},
@@ -9386 +9754 @@
 
 In fact, nearly all archive member targets are updated in just this way
-and there is an implicit rule to do it for you.  @strong{Note:} The
+and there is an implicit rule to do it for you.  @strong{Please note:} The
 @samp{c} flag to @code{ar} is required if the archive file does not
 already exist.
@@ -10124 +10492 @@
 @xref{Origin Function, , The @code{origin} Function}.
 
+@item $(flavor @var{variable})
+
+Return a string describing the flavor of the @code{make} variable
+@var{variable}.@*
+@xref{Flavor Function, , The @code{flavor} Function}.
+
 @item $(foreach @var{var},@var{words},@var{text})
 
@@ -10133 +10507 @@
 
 Evaluate the variable @var{var} replacing any references to @code{$(1)},
-@code{$(2)} with the first, second, etc. @var{param} values.@*
+@code{$(2)} with the first, second, etc.@: @var{param} values.@*
 @xref{Call Function, ,The @code{call} Function}.
 
@@ -10228 +10602 @@
 commands.  @xref{Execution, ,Command Execution}.  The @code{SHELL}
 variable is handled specially when importing from and exporting to the
-environment.  @xref{Environment, ,Using Variable from the Environment}.
+environment.  @xref{Choosing the Shell}.
 
 @item MAKESHELL
 
 On MS-DOS only, the name of the command interpreter that is to be used
-by @code{make}. This value takes precedence over the value of
+by @code{make}.  This value takes precedence over the value of
 @code{SHELL}.  @xref{Execution, ,MAKESHELL variable}.
 
@@ -10728 +11102 @@
 @printindex fn
 
-@summarycontents
-@contents
 @bye