[PATCH 2/3] automake.texi

[William Pursell]

commit fd35df2e912466f17d393628dc4b71456badd5e8
Author: William Pursell <address@hidden>
Date:   Sat Nov 22 12:40:02 2008 +0000

    Minor edits of automake.texi of questionable quality.

diff --git a/doc/automake.texi b/doc/automake.texi
index 3d12c61..55c417c 100644
--- a/doc/automake.texi
+++ b/doc/automake.texi
@@ -2310,6 +2310,9 @@ implicitly assume that there is a source file named 
@file{true.c}, and
 define rules to compile @file{true.o} and link @file{true}.  The
 @samp{true.o: true.c} rule supplied by the above @file{Makefile.am},
 will override the Automake generated rule to build @file{true.o}.
address@hidden Perhaps an explicit reference to AM_DEFAULT_SOURCE_EXT
address@hidden is appropriate here.
+(@pxref{Default _SOURCES})

 @code{false_SOURCES} is defined to be empty---that way no implicit value
 is substituted.  Because we have not listed the source of
@@ -2886,8 +2889,9 @@ If a Lex source file is seen, then this macro must be 
used.
 Autoconf Manual}.

 @item AC_REQUIRE_AUX_FILE
address@hidden will ensure each file for which this macro is
-called exists in the aux directory, and will complain otherwise.  It
address@hidden will look in the aux directory
+for each file on which this macro is invoked and will complain if
+the file does not exist.  It
 will also automatically distribute the file.  This macro should be
 used by third-party Autoconf macros that requires some supporting
 files in the aux directory specified with @code{AC_CONFIG_AUX_DIR}
@@ -2900,8 +2904,10 @@ generated @file{Makefile.in}, unless 
@code{AM_SUBST_NOTMAKE} is also
 used for this variable.  @xref{Setting Output Variables, , Setting
 Output Variables, autoconf, The Autoconf Manual}.

+Several macros invoke @code{AC_SUBST} and cause certain
+variables to be defined in each generated Makefile.in.
 If the Autoconf manual says that a macro calls @code{AC_SUBST} for
address@hidden, or defines the output variable @var{var} then @var{var} will
address@hidden or defines the output variable @var{var}, then @var{var} will
 be defined in each @file{Makefile.in} generated by Automake.
 E.g.@: @code{AC_PATH_XTRA} defines @code{X_CFLAGS} and @code{X_LIBS}, so
 you can use these variables in any @file{Makefile.am} if

                                                                                
                 22/11  1:12pm

--
William Pursell