* doc/automake.texi (Dist): Document limitations of distcheck-hook

and DISTCHECK_CONFIGURE_FLAGS with regard to subdirs and
subpackages.

diff --git a/ChangeLog b/ChangeLog
index 0403552717853bc3df1e37a594b0b7c8f3db87ec..32b381eb454387b3a77de4e9536fc428cb971240 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2004-01-20  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>  (tiny change)
+
+       * doc/automake.texi (Dist): Document limitations of distcheck-hook
+       and DISTCHECK_CONFIGURE_FLAGS with regard to subdirs and
+       subpackages.
+
 2004-01-20  Alexandre Duret-Lutz  <adl@gnu.org>
 
        * doc/automake.texi (Upgrading): New node.

diff --git a/doc/automake.texi b/doc/automake.texi
index ae2ae5589380891955a3b6b649a8e87919bcc157..1f517396f457a5fea6bb4b5e844e41442b0e4bab 100644 (file)
--- a/doc/automake.texi
+++ b/doc/automake.texi
@@ -5365,13 +5365,17 @@ to supply additional flags to @code{configure}, define them in the
 @file{Makefile.am}, or on the command line when invoking @code{make}.
 @vindex DISTCHECK_CONFIGURE_FLAGS
 
-If the @code{distcheck-hook} rule is defined in your
+If the @code{distcheck-hook} rule is defined in your top-level
 @file{Makefile.am}, then it will be invoked by @code{distcheck} after
 the new distribution has been unpacked, but before the unpacked copy
 is configured and built.  Your @code{distcheck-hook} can do almost
 anything, though as always caution is advised.  Generally this hook is
 used to check for potential distribution errors not caught by the
-standard mechanism.
+standard mechanism.  Note that @code{distcheck-hook} as well as
+@code{DISTCHECK_CONFIGURE_FLAGS} are not honored in a subpackage
+@file{Makefile.am}, but the @code{DISTCHECK_CONFIGURE_FLAGS} are
+passed down to the @code{configure} script of the subpackage.
+
 
 Speaking about potential distribution errors, @code{distcheck} will also
 ensure that the @code{distclean} rule actually removes all built