From: Tom Tromey <tromey@redhat.com>
Date: Mon, 1 Jun 1998 20:24:42 +0000 (+0000)
Subject: Fixed check buglet
X-Git-Tag: Release-1-3b~23
X-Git-Url: https://sourceware.org/git/?a=commitdiff_plain;h=f66d479e262e1657813b7781e6122ca6b74e17ee;p=automake.git

Fixed check buglet
---

diff --git a/ChangeLog b/ChangeLog
index 9460a6c3..cb4983d9 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+Mon Jun  1 14:23:29 1998  Tom Tromey  <tromey@cygnus.com>
+
+	* automake.in (do_check_merge_target): Only generate $(MAKE)
+	command if there are check targets to make.
+
 Sun May 17 23:05:55 1998  Tom Tromey  <tromey@cygnus.com>
 
 	* aclocal.in (write_aclocal): Fixed generated copyright message.
diff --git a/automake.in b/automake.in
index cf9bc812..74fb984c 100755
--- a/automake.in
+++ b/automake.in
@@ -3667,8 +3667,11 @@ sub do_check_merge_target
     # @check_tests.  This is done via a separate make invocation to
     # avoid problems with parallel makes.  Every time I write code
     # like this I wonder: how could you invent a parallel make and not
-    # provide any real synchronization facilities?
-    &pretty_print_rule ("\t\$(MAKE)", "\t  ", @check_tests);
+    # provide any real synchronization facilities?  The official
+    # answer is that you can push the dependencies out to the leaves
+    # of the dependency tree.  That seems fairly gross to me.
+    &pretty_print_rule ("\t\$(MAKE)", "\t  ", @check_tests)
+	if @check_tests;
 }
 
 # Handle all 'clean' targets.