Re: building HEAD needs GNU make

[Ralf Wildenhues]

* Eric Blake wrote on Sat, Feb 24, 2007 at 02:03:43PM CET:
> According to Ralf Wildenhues on 2/24/2007 5:55 AM:
> > 
> > Do you think using the string `gmake' is ok/helpful/bad?
> 
> Not every platform has gmake by default (for example, cygwin comes with
> GNU make only installed as "make"), but it is a common enough idiom that
> developers should be able to figure it out.  Maybe it is worth adding a
> note up front that gmake refers to the user's installation of GNU make?

Good idea.  Done like this.  I'll also put the GNU make requirement into
the "regressions that may be fixed" part of NEWS.

Cheers,
Ralf

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

        * 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.

Index: README
===================================================================
RCS file: /cvsroot/libtool/libtool/README,v
retrieving revision 1.26
diff -u -r1.26 README
--- README      30 Aug 2006 03:18:15 -0000      1.26
+++ README      24 Feb 2007 13:21:51 -0000
@@ -8,7 +8,7 @@
 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 @@
 
   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 <address@hidden> or bug reports to <address@hidden>.  Be sure
 to send us your information from the end of the help message given by
@@ -39,10 +40,18 @@
 ==================
 
 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 @@
 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 @@
 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 @@
 
 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
Index: README.alpha
===================================================================
RCS file: /cvsroot/libtool/libtool/README.alpha,v
retrieving revision 1.10
diff -u -r1.10 README.alpha
--- README.alpha        30 Aug 2006 03:18:15 -0000      1.10
+++ README.alpha        24 Feb 2007 13:21:51 -0000
@@ -8,7 +8,11 @@
 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 <address@hidden> with a
 subject line including the string `[PLATFORM]'.
 
@@ -42,10 +46,18 @@
 ==================
 
 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:
+
+  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:
 
-  make check TESTSUITEFLAGS=-V
-  make check-local
+  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 @@
 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 @@
 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 @@
 
 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
Index: doc/notes.texi
===================================================================
RCS file: /cvsroot/libtool/libtool/doc/notes.texi,v
retrieving revision 1.2
diff -u -r1.2 notes.texi
--- doc/notes.texi      24 Feb 2007 08:46:19 -0000      1.2
+++ doc/notes.texi      24 Feb 2007 13:21:51 -0000
@@ -1,6 +1,9 @@
 @itemize
 
 @item
+You currently need GNU make to build the Libtool package itself.
+
address@hidden
 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,
 similar to address@hidden  In case of doubt use @code{LDFLAGS=-Wl,-brtl} for 
the latter style.
@@ -16,10 +19,10 @@
 10.3 or later at @command{configure} time.  See @url{rdar://problem/4135857}
 for more information on this issue.
 
address@hidden
-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.
address@hidden @item
address@hidden FreeBSD @command{make} does not conform to @sc{posix} in its 
handling
address@hidden of file modification times, which causes it to loop while 
building libtool.
address@hidden 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