* doc/automake.texi (Scripts): Fix some errors in previous patch.

diff --git a/ChangeLog b/ChangeLog
index 435d028..7a811f4 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2006-08-04  Alexandre Duret-Lutz  <adl@gnu.org>
 
+       * doc/automake.texi (Scripts): Fix some errors in previous patch.
+
        * doc/automake.texi (Scripts): Revamp.  Show an example of script
        built from configure.ac.  Discuss CLEANFILES and EXTRA_DIST for
        other built scripts.

diff --git a/doc/automake.texi b/doc/automake.texi
index ae013d5..c67b7f9 100644 (file)
--- a/doc/automake.texi
+++ b/doc/automake.texi
@@ -5364,25 +5364,29 @@ the rebuild rules should look like.
 For instance if @file{configure.ac} contains
 
 @example
-AC_CONFIG_FILES([src/my_script])
+AC_CONFIG_FILES([src/my_script], [chmod +x src/my_script])
 @end example
 
 @noindent
-to build @file{src/my_script} from @file{src/my_script}, then an
+to build @file{src/my_script} from @file{src/my_script.in}, then an
 @file{src/Makefile.am} to install this script in @code{$(bindir)} can
 be as simple as
 
 @example
 bin_SCRIPTS = my_script
+CLEANFILES = $(bin_SCRIPTS)
 @end example
 
 @noindent
-There is no need for @code{EXTRA_DIST}, @code{CLEANFILES}, or any
-build rule: Automake infers them from @code{AC_CONFIG_FILES}
-(@pxref{Requirements}).  This looks simpler, however building scripts
-this way has one drawback: directory variables such as
-@code{$(datadir)} are not fully expanded and may refer to other
-directory variables.
+There is no need for @code{EXTRA_DIST} or any build rule: Automake
+infers them from @code{AC_CONFIG_FILES} (@pxref{Requirements}).
+@code{CLEANFILES} is still useful, because by default Automake will
+clean targets of @code{AC_CONFIG_FILES} in @code{distclean}, not
+@code{clean}.
+
+Although this looks simpler, building scripts this way has one
+drawback: directory variables such as @code{$(datadir)} are not fully
+expanded and may refer to other directory variables.
 
 @node Headers
 @section Header files