Rename 'test' to 'check' target in Makefile.direct

(Cherry-pick commit 4fad4e5 from 'master' branch.)

This is to match the target name in Makefile generated by configure.

* Makefile.direct: Update comment about testing (rename "test" target
to "check").
* Makefile.direct (check): Renamed from "test".
* Makefile.direct (test): Depend on check; add comment.
* README.QUICK (INSTALLATION): Leave information only about the recent
GC version.
* README.QUICK (INSTALLATION): Replace "make test" with "make check".
* README.md (Installation and Portability): Likewise.

diff --git a/Makefile.direct b/Makefile.direct
index ac906fa58b349317c2c38f6414cda09ec8983383..1355398d6a0193af9a7d1071307f59a962828f59 100644 (file)
--- a/Makefile.direct
+++ b/Makefile.direct
@@ -5,9 +5,9 @@
 # gc.a - builds basic library
 # c++ - adds C++ interface to library
 # cords - adds cords (heavyweight strings) to library
-# test - prints porting information, then builds basic version of gc.a,
-#        and runs some tests of collector and cords.  Does not add cords or
-#        c++ interface to gc.a
+# check - prints porting information, then builds basic version of gc.a,
+#       and runs some tests of collector and cords.  Does not add cords or
+#       c++ interface to gc.a
 # cord/de - builds dumb editor based on cords.
 
 ABI_FLAG=
@@ -409,7 +409,7 @@ gctest: tests/test.o base_lib $(UTILS)
 setjmp_test: $(srcdir)/tools/setjmp_t.c $(srcdir)/include/gc.h $(UTILS)
        $(CC) $(CFLAGS) -o setjmp_test $(srcdir)/tools/setjmp_t.c
 
-test: KandRtest cord/cordtest
+check: KandRtest cord/cordtest
        cord/cordtest
 
 # Those tests that work even with a K&R C compiler:
@@ -417,6 +417,9 @@ KandRtest: setjmp_test gctest
        ./setjmp_test
        ./gctest
 
+# A synonym to "check" (for compatibility with older GC versions).
+test: check
+
 add_gc_prefix: $(srcdir)/tools/add_gc_prefix.c $(srcdir)/include/gc_version.h
        $(CC) -o add_gc_prefix $(srcdir)/tools/add_gc_prefix.c
 

diff --git a/README.QUICK b/README.QUICK
index 26ddcf9b53879d9100e02ff697bbc278d6548400..3782cbd01130f2d821a0b05ca1fb538a84d6b976 100644 (file)
--- a/README.QUICK
+++ b/README.QUICK
@@ -26,10 +26,8 @@ For the version number, see README.md or include/gc_version.h files.
 
 INSTALLATION:
 Under UN*X, Linux:
-Alternative 1 (the old way): type "make test" in this directory.
-        Link against gc.a.  With the most recent GC distributions
-        you may have to type "make -f Makefile.direct test" or
-        copy Makefile.direct to Makefile first.
+Alternative 1 (the old way): type "make -f Makefile.direct check".
+        Link against gc.a.
 
 Alternative 2 (the new way): type
         "./configure --prefix=<dir>; make; make check; make install".

diff --git a/README.md b/README.md
index 433b6097bda2c2d3594377007325364bf70a9f08..17696401e030a7afc51b6c7234695cdab0b846cc 100644 (file)
--- a/README.md
+++ b/README.md
@@ -189,7 +189,7 @@ configure execution, this means pkg.m4 cannot be found, most probably
 you should run `pkg-config` once before running `./autogen.sh` (autoreconf).
 
 Below we focus on the collector build using classic makefile.
-For the Makefile.direct-based process, typing `make test` instead of `make`
+For the Makefile.direct-based process, typing `make check` instead of `make`
 will automatically build the collector and then run `setjmp_test` and `gctest`.
 `Setjmp_test` will give you information about configuring the collector, which is
 useful primarily if you have a machine that's not already supported.  Gctest is