From 2c25fb4d3c3a47c9c694f64edb09776078efcd71 Mon Sep 17 00:00:00 2001 From: Ralf Wildenhues Date: Sun, 25 Feb 2007 15:33:24 +0000 Subject: [PATCH] * README: Document the need for GNU make to build Libtool. Point the user to the doc/notes.txt file. In the examples, use `gmake' throughout to make it more obvious. Explain simpler way to run both testsuites and either one. Referring to individual tests needs the `tests/' prefix. * README.alpha: Likewise. * doc/notes.texi: Likewise, document need for GNU make. Comment out the FreeBSD make issue for now. --- ChangeLog | 9 +++++++++ README | 38 ++++++++++++++++++++++++-------------- README.alpha | 31 ++++++++++++++++++++++--------- doc/notes.texi | 11 +++++++---- 4 files changed, 62 insertions(+), 27 deletions(-) diff --git a/ChangeLog b/ChangeLog index 46b0ced8..2f6b1fbf 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,14 @@ 2007-02-25 Ralf Wildenhues + * README: Document the need for GNU make to build Libtool. + Point the user to the doc/notes.txt file. In the examples, use + `gmake' throughout to make it more obvious. Explain simpler way + to run both testsuites and either one. Referring to individual + tests needs the `tests/' prefix. + * README.alpha: Likewise. + * doc/notes.texi: Likewise, document need for GNU make. + Comment out the FreeBSD make issue for now. + * tests/static.at: Larger rewrite to make work on w32: Use three different prefixes instead of three libdirs, so the moving of the DLLs works as expected. Adjust all code. Since now diff --git a/README b/README index e8aa02f4..262dcafb 100644 --- a/README +++ b/README @@ -8,7 +8,7 @@ This is GNU Libtool, a generic library support script. Libtool hides the complexity of using shared libraries behind a consistent, portable interface. -To use libtool, add the new generic library building commands to your +To use Libtool, add the new generic library building commands to your Makefile, Makefile.in, or Makefile.am. See the documentation for details. @@ -16,19 +16,20 @@ Libtool's home page is: http://www.gnu.org/software/libtool/libtool.html -See the file NEWS for a description of recent changes to libtool. +See the file NEWS for a description of recent changes to Libtool. -See the file INSTALL for instructions on how to build and install -libtool. +See the file INSTALL for generic instructions on how to build and install +Libtool. Please see the file doc/notes.txt for some platform-specific +information. Please note that you need GNU make to build Libtool. See the info node (libtool)Tested Platforms. (or the file -doc/PLATFORMS) for a list of platforms that libtool supports. +doc/PLATFORMS) for a list of platforms that Libtool supports. 2. Reporting Bugs ================= -If you have any suggestions or bug reports, or you wish to port libtool +If you have any suggestions or bug reports, or you wish to port Libtool to a new platform, please send electronic mail to the libtool mailing list or bug reports to . Be sure to send us your information from the end of the help message given by @@ -39,10 +40,18 @@ to send us your information from the end of the help message given by ================== Libtool comes with two integrated sets of tests to check that your build -is sane. You can run both test suites like this: +is sane. You can run both test suites like this, assuming that `gmake' +refers to GNU make: - make check TESTSUITEFLAGS=-V - make check-local + gmake -k check + +If you want to run the old testsuite only, do it like this: + + gmake check TESTSUITEFLAGS=-V + +If you want to run the new testsuite only, do it like this: + + gmake check-local The tests of the old test suite run in groups in the various demo subdirectories, so if one of the tests early in a group FAILs, the rest @@ -55,8 +64,9 @@ To run a test group of the old test suite in isolation (say, you think you have fixed a bug, but don't want to rerun the entire suite), you can do it like this: - make check TESTS='cdemo-static.test cdemo-make.test cdemo-exec.test' \ - TESTSUITEFLAGS=-V + gmake check TESTS="tests/cdemo-static.test tests/cdemo-make.test \ + tests/cdemo-exec.test" \ + TESTSUITEFLAGS=-V Providing that you have a FAIL from the most recent group from a particular demo directory (like the cdemo-static.test group above), you @@ -69,8 +79,8 @@ report mailing list, with a subject line that includes the string `[TEST FAILURE]'. From a Bourne compatible shell, you can generate verbose test output like this: - VERBOSE=yes make check \ - TESTS='cdemo-static.test cdemo-make.test cdemo-exec.test' \ + VERBOSE=yes gmake check \ + TESTS="tests/cdemo-static.test tests/cdemo-make.test tests/cdemo-exec.test" \ TESTSUITEFLAGS=-V | tee cdemo-static-group.log In order to enable debug shell tracing, use VERBOSE=debug instead of @@ -84,7 +94,7 @@ Autotest-driven testsuite. Its usage is documented in but simple help may also be obtained through - make check-local TESTSUITEFLAGS='--help' + gmake check-local TESTSUITEFLAGS='--help' For verbose output, add the flag `-v', for running only a subset of the independent tests, merely specify them by number or by keyword, both of diff --git a/README.alpha b/README.alpha index fc080460..22340e67 100644 --- a/README.alpha +++ b/README.alpha @@ -8,7 +8,11 @@ This is an alpha testing release of GNU Libtool, please try it on all the platforms you have access to. Using it more or less implicitly signs you up to help us find whatever problems you report. -If it builds and passes the test suite (`make check'), please send +See the file INSTALL for generic instructions on how to build and install +Libtool. Please see the file doc/notes.txt for some platform-specific +information. Please note that you need GNU make to build Libtool. + +If it builds and passes the test suite (`gmake check'), please send notification to the libtool mailing list with a subject line including the string `[PLATFORM]'. @@ -42,10 +46,18 @@ of any failed test groups (as described below). ================== Libtool comes with two integrated sets of tests to check that your build -is sane. You can run both test suites like this: +is sane. You can run both test suites like this, assuming that `gmake' +refers to GNU make: - make check TESTSUITEFLAGS=-V - make check-local + gmake -k check + +If you want to run the old testsuite only, do it like this: + + gmake check TESTSUITEFLAGS=-V + +If you want to run the new testsuite only, do it like this: + + gmake check-local The tests of the old test suite run in groups in the various demo subdirectories, so if one of the tests early in a group FAILs, the rest @@ -58,8 +70,9 @@ To run a test group of the old test suite in isolation (say, you think you have fixed a bug, but don't want to rerun the entire suite), you can do it like this: - make check TESTS='cdemo-static.test cdemo-make.test cdemo-exec.test' \ - TESTSUITEFLAGS=-V + gmake check TESTS="tests/cdemo-static.test tests/cdemo-make.test \ + tests/cdemo-exec.test" \ + TESTSUITEFLAGS=-V Providing that you have a FAIL from the most recent group from a particular demo directory (like the cdemo-static.test group above), you @@ -72,8 +85,8 @@ report mailing list, with a subject line that includes the string `[TEST FAILURE]'. From a Bourne compatible shell, you can generate verbose test output like this: - VERBOSE=yes make check \ - TESTS='cdemo-static.test cdemo-make.test cdemo-exec.test' \ + VERBOSE=yes gmake check \ + TESTS="tests/cdemo-static.test tests/cdemo-make.test tests/cdemo-exec.test" \ TESTSUITEFLAGS=-V | tee cdemo-static-group.log In order to enable debug shell tracing, use VERBOSE=debug instead of @@ -87,7 +100,7 @@ Autotest-driven testsuite. Its usage is documented in but simple help may also be obtained through - make check-local TESTSUITEFLAGS='--help' + gmake check-local TESTSUITEFLAGS='--help' For verbose output, add the flag `-v', for running only a subset of the independent tests, merely specify them by number or by keyword, both of diff --git a/doc/notes.texi b/doc/notes.texi index ec205826..995c9f97 100644 --- a/doc/notes.texi +++ b/doc/notes.texi @@ -1,5 +1,8 @@ @itemize +@item +You currently need GNU make to build the Libtool package itself. + @item On AIX there are two different styles of shared linking, one in which symbols are bound at link-time and one in which symbols are bound at runtime only, @@ -16,10 +19,10 @@ Libtool builds these by default if @env{MACOSX_DEPLOYMENT_TARGET} is set to 10.3 or later at @command{configure} time. See @url{rdar://problem/4135857} for more information on this issue. -@item -FreeBSD @command{make} does not conform to @sc{posix} in its handling -of file modification times, which causes it to loop while building libtool. -Consider using a different @command{such} as GNU make instead. +@c @item +@c FreeBSD @command{make} does not conform to @sc{posix} in its handling +@c of file modification times, which causes it to loop while building libtool. +@c Consider using a different @command{such} as GNU make instead. @item The default shell on UNICOS 9, a ksh 88e variant, is too buggy to