* doc/autoconf.texi (Making testsuite Scripts): Add an example

how to use TESTSUITEFLAGS.  Suggested by Eric Blake.

diff --git a/ChangeLog b/ChangeLog
index 4a90155f2746c3c33e6eaaa8a1aaef889cdd653e..d0a5b66a0eab59ee6300ce4297b27053f8b8bd31 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2006-05-25  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
+
+       * doc/autoconf.texi (Making testsuite Scripts): Add an example
+       how to use TESTSUITEFLAGS.  Suggested by Eric Blake.
+
 2006-05-24  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
 
        * tests/autotest.at (Multiline command from M4 expansion):

diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index 1c94056c928e4b580e4bd7a26c7ae15e974e7334..34d19df15abd4a6e9b5ce8216b105089fdee3a7c 100644 (file)
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -17644,6 +17644,14 @@ atlocal: $(srcdir)/atlocal.in $(top_builddir)/config.status
 and manage to have @file{atconfig.in} and @code{$(EXTRA_DIST)}
 distributed.
 
+With all this in place, and if you have not initialized @samp{TESTSUITEFLAGS}
+within your Makefile, you can fine-tune test suite execution with this variable,
+for example:
+
+@example
+make check TESTSUITEFLAGS='-v -d -x 75 -k AC_PROG_CC CFLAGS=-g'
+@end example
+
 
 
 @c =============================== Frequent Autoconf Questions, with answers