FYI: another update of libtool.texi old testsuite doc

[Ralf Wildenhues]

This should now describe the old testsuite more or less correctly
and give at least a pointer towards help for the new testsuite.

Applied to HEAD.

Cheers,
Ralf

2007-02-24  Ralf Wildenhues  <address@hidden>

        * doc/libtool.texi (Libtool test suite): Mention the new
        testsuite.  Point to README rather than INSTALL for testing
        instructions.
        (Test descriptions): Fix more file names.  Also mention
        cdemo-undef.test, mdemo2-conf.test, mdemo2-exec.test,
        mdemo2-make.test, objectlist.test, pdemo-conf.test,
        pdemo-exec.test, pdemo-inst.test, pdemo-make.test,
        tagdemo-conf.test, tagdemo-exec.test, tagdemo-make.test,
        tagdemo-static.test, tagdemo-shared.test, tagdemo-undef.test,
        f77demo-conf.test, f77demo-exec.test, f77demo-make.test,
        f77demo-static.test, f77demo-shared.test, fcdemo-conf.test,
        fcdemo-exec.test, fcdemo-make.test, fcdemo-static.test,
        fcdemo-shared.test.  Describe what they do.
        (When tests fail, Troubleshooting): Mention how to pass options
        to the new test suite.
        * tests/tagdemo/README: Fix description.

Index: doc/libtool.texi
===================================================================
RCS file: /cvsroot/libtool/libtool/doc/libtool.texi,v
retrieving revision 1.222
diff -u -r1.222 libtool.texi
--- doc/libtool.texi    24 Feb 2007 14:49:53 -0000      1.222
+++ doc/libtool.texi    24 Feb 2007 15:58:38 -0000
@@ -4600,25 +4606,26 @@
 @section The libtool test suite
 @cindex test suite
 
-Libtool comes with its own set of programs that test its capabilities,
-and report obvious bugs in the libtool program.  These tests, too, are
-constantly evolving, based on past problems with libtool, and known
-deficiencies in other operating systems.
+Libtool comes with two integrated sets of tests to check that your build
+is sane, that test its capabilities, and report obvious bugs in the
+libtool program.  These tests, too, are constantly evolving, based on
+past problems with libtool, and known deficiencies in other operating
+systems.
 
-As described in the @file{INSTALL} file, you may run @kbd{make check}
+As described in the @file{README} file, you may run @kbd{make -k check}
 after you have built libtool (possibly before you install it) in order
 to make sure that it meets basic functional requirements.
 
 @menu
-* Test descriptions::           The contents of the test suite.
+* Test descriptions::           The contents of the old test suite.
 * When tests fail::             What to do when a test fails.
 @end menu
 
 @node Test descriptions
 @subsection Description of test suite
 
-Here is a list of the current programs in the test suite, and what they
-test for:
+Here is a list of the current programs in the old test suite, and what
+they test for:
 
 @table @file
 
@@ -4627,15 +4634,17 @@
 @itemx cdemo-make.test
 @itemx cdemo-static.test
 @itemx cdemo-shared.test
address@hidden cdemo-undef.test
 @pindex cdemo-conf.test
 @pindex cdemo-exec.test
 @pindex cdemo-make.test
 @pindex cdemo-static.test
 @pindex cdemo-shared.test
-These programs check to see that the @file{cdemo} subdirectory of the
-libtool distribution can be configured and built correctly.
address@hidden cdemo-undef.test
+These programs check to see that the @file{tests/cdemo} subdirectory of
+the libtool distribution can be configured and built correctly.
 
-The @file{cdemo} subdirectory contains a demonstration of libtool
+The @file{tests/cdemo} subdirectory contains a demonstration of libtool
 convenience libraries, a mechanism that allows build-time static
 libraries to be created, in a way that their components can be later
 linked into programs or other libraries, even shared ones.
@@ -4648,6 +4657,9 @@
 (@samp{--disable-shared}), and @file{cdemo-shared.test} builds only
 shared libraries (@samp{--disable-static}).
 
+The test @file{cdemo-undef.test} tests the generation of shared
+libraries with undefined symbols on systems that allow this.
+
 @item demo-conf.test
 @itemx demo-exec.test
 @itemx demo-inst.test
@@ -4668,11 +4680,11 @@
 @pindex demo-nofast.test
 @pindex demo-pic.test
 @pindex demo-nopic.test
-These programs check to see that the @file{demo} subdirectory of the
-libtool distribution can be configured, built, installed, and
+These programs check to see that the @file{tests/demo} subdirectory of
+the libtool distribution can be configured, built, installed, and
 uninstalled correctly.
 
-The @file{demo} subdirectory contains a demonstration of a trivial
+The @file{tests/demo} subdirectory contains a demonstration of a trivial
 package that uses libtool.  The tests @file{demo-make.test},
 @file{demo-exec.test}, @file{demo-inst.test} and
 @file{demo-unst.test} are executed four times, under four different
@@ -4731,13 +4743,13 @@
 @pindex depdemo-static.test
 @pindex depdemo-shared.test
 @pindex depdemo-nofast.test
-These programs check to see that the @file{depdemo} subdirectory of the
-libtool distribution can be configured, built, installed, and
+These programs check to see that the @file{tests/depdemo} subdirectory
+of the libtool distribution can be configured, built, installed, and
 uninstalled correctly.
 
-The @file{depdemo} subdirectory contains a demonstration of inter-library
-dependencies with libtool.  The test programs link some interdependent
-libraries.
+The @file{tests/depdemo} subdirectory contains a demonstration of
+inter-library dependencies with libtool.  The test programs link some
+interdependent libraries.
 
 The tests @file{depdemo-make.test}, @file{depdemo-exec.test},
 @file{depdemo-inst.test} and @file{depdemo-unst.test} are executed
@@ -4763,15 +4775,15 @@
 @pindex mdemo-unst.test
 @pindex mdemo-static.test
 @pindex mdemo-shared.test
-These programs check to see that the @file{mdemo} subdirectory of the
-libtool distribution can be configured, built, installed, and
+These programs check to see that the @file{tests/mdemo} subdirectory of
+the libtool distribution can be configured, built, installed, and
 uninstalled correctly.
 
-The @file{mdemo} subdirectory contains a demonstration of a package that
-uses libtool and the system independent dlopen wrapper @file{libltdl} to
-load modules.  The library @file{libltdl} provides a dlopen wrapper for
-various platforms (Linux, Solaris, HP/UX etc.) including support for
-dlpreopened modules (@pxref{Dlpreopening}).
+The @file{tests/mdemo} subdirectory contains a demonstration of a
+package that uses libtool and the system independent dlopen wrapper
address@hidden to load modules.  The library @file{libltdl} provides a
+dlopen wrapper for various platforms (Linux, Solaris, HP/UX etc.)
+including support for dlpreopened modules (@pxref{Dlpreopening}).
 
 The tests @file{mdemo-make.test}, @file{mdemo-exec.test},
 @file{mdemo-inst.test} and @file{mdemo-unst.test} are executed
@@ -4785,6 +4797,20 @@
 @pindex mdemo-dryrun.test
 This test checks whether libtool's @option{--dry-run} mode works properly.
 
address@hidden mdemo2-conf.test
address@hidden mdemo2-exec.test
address@hidden mdemo2-make.test
address@hidden mdemo2-conf.test
address@hidden mdemo2-exec.test
address@hidden mdemo2-make.test
+These programs check to see that the @file{tests/mdemo2} subdirectory of
+the libtool distribution can be configured, built, and executed
+correctly.
+
+The @file{tests/mdemo2} directory contains a demonstration of a package
+that attempts to link with a library (from the @file{tests/mdemo}
+directory) that itself does dlopening of libtool modules.
+
 @item link.test
 @pindex link.test
 This test guarantees that linking directly against a non-libtool static
@@ -4799,6 +4825,26 @@
 @pindex nomode.test
 Check whether we can actually get help for libtool.
 
address@hidden objectlist.test
address@hidden objectlist.test
+Check that a nonexistent objectlist file is properly 
+
address@hidden pdemo-conf.test
address@hidden pdemo-exec.test
address@hidden pdemo-inst.test
address@hidden pdemo-make.test
address@hidden pdemo-conf.test
address@hidden pdemo-exec.test
address@hidden pdemo-inst.test
address@hidden pdemo-make.test
+These programs check to see that the @file{tests/pdemo} subdirectory of
+the libtool distribution can be configured, built, and executed
+correctly.
+
+The @file{pdemo-conf.test} lowers the @var{max_cmd_len} variable in the
+generated libtool script to test the measures to evade command line
+length limitations.
+
 @item quote.test
 @pindex quote.test
 This program checks libtool's metacharacter quoting.
@@ -4815,6 +4861,64 @@
 This test validates that libtool can handle suffixes for all the file
 types that it supports, and that it fails when the suffix is invalid.
 
address@hidden tagdemo-conf.test
address@hidden tagdemo-exec.test
address@hidden tagdemo-make.test
address@hidden tagdemo-static.test
address@hidden tagdemo-shared.test
address@hidden tagdemo-undef.test
address@hidden tagdemo-conf.test
address@hidden tagdemo-exec.test
address@hidden tagdemo-make.test
address@hidden tagdemo-static.test
address@hidden tagdemo-shared.test
address@hidden tagdemo-undef.test
+These programs check to see that the @file{tests/tagdemo} subdirectory
+of the libtool distribution can be configured, built, and executed
+correctly.
+
+The @file{tests/tagdemo} directory contains a demonstration of a package
+that uses libtool's multi-language support through configuration tags.
+It generates a library from C++ sources, which is then linked to a C++
+program.
+
address@hidden f77demo-conf.test
address@hidden f77demo-exec.test
address@hidden f77demo-make.test
address@hidden f77demo-static.test
address@hidden f77demo-shared.test
address@hidden f77demo-conf.test
address@hidden f77demo-exec.test
address@hidden f77demo-make.test
address@hidden f77demo-static.test
address@hidden f77demo-shared.test
+These programs check to see that the @file{tests/f77demo} subdirectory
+of the libtool distribution can be configured, built, and executed
+correctly.
+
+The @file{tests/f77demo} tests test Fortran 77 support in libtool by
+creating libraries from Fortran 77 sources, and mixed Fortran and C
+sources, and a Fortran 77 program to use the former library, and a C
+program to use the latter library.
+
address@hidden fcdemo-conf.test
address@hidden fcdemo-exec.test
address@hidden fcdemo-make.test
address@hidden fcdemo-static.test
address@hidden fcdemo-shared.test
address@hidden fcdemo-conf.test
address@hidden fcdemo-exec.test
address@hidden fcdemo-make.test
address@hidden fcdemo-static.test
address@hidden fcdemo-shared.test
+These programs check to see that the @file{tests/fcdemo} subdirectory
+of the libtool distribution can be configured, built, and executed
+correctly.
+
+The @file{tests/fcdemo} is similar to the @file{tests/f77demo}
+directory, except that Fortran 90 is used in combination with the
address@hidden interface provided by Autoconf and Automake.
+
 @end table
 
 @node When tests fail
@@ -4822,9 +4926,9 @@
 @cindex failed tests
 @cindex tests, failed
 
-Each of the above tests are designed to produce no output when they are
-run via @kbd{make check}.  The exit status of each program tells the
address@hidden whether or not the test succeeded.
+Each of the tests in the old test suite are designed to produce no
+output when they are run via @kbd{make check}.  The exit status of each
+program tells the @file{Makefile} whether or not the test succeeded.
 
 If a test fails, it means that there is either a programming error in
 libtool, or in the test program itself.
@@ -4838,6 +4942,15 @@
 For example, @kbd{env VERBOSE=yes make check} runs all the tests, and
 has each of them display debugging information.
 
+The new, Autotest-based test suite produces as output a file
address@hidden/testsuite.log} which contains information about failed
+tests.
+
+You can pass options to the test suite through the @command{make}
+variable @var{TESTSUITEFLAGS} (@pxref{testsuite Invocation, ,
+The Autoconf Manual, autoconf, The Autoconf Manual}).
+
+
 @node Reporting bugs
 @section Reporting bugs
 @cindex bug reports
Index: tests/tagdemo/README
===================================================================
RCS file: /cvsroot/libtool/libtool/tests/tagdemo/README,v
retrieving revision 1.1
diff -u -r1.1 README
--- tests/tagdemo/README        14 Oct 2003 21:46:13 -0000      1.1
+++ tests/tagdemo/README        24 Feb 2007 15:58:39 -0000
@@ -4,5 +4,5 @@
 GNU Libtool's multi-language support through the use of configuration
 tags.  It requires GNU autoconf, automake and of course libtool.
 
-The demonstration generates a libraries using the same libtool script,
-which is then linked to a C++ program.
+The demonstration generates a library from C++ sources, which is then
+linked to a C++ program.