autoreconf should run automake after aclocal

[Andreas Schwab]

automake should only run after aclocal, because automake depends on
uptodate macros for deciding what needs to be installed with
--add-missing.  For example, libtoolize or gettextize might add new macros
that require to run config.sub when it wasn't necessary before.

Andreas.

2002-03-30  Andreas Schwab  <address@hidden>

        * bin/autoreconf.in (autoreconf): Run automake after rerunning
        aclocal.

--- bin/autoreconf.in.~1.90.~   2002-03-30 21:32:59.000000000 +0100
+++ bin/autoreconf.in   2002-03-30 21:35:31.000000000 +0100
@@ -426,24 +426,6 @@
     }
 
 
-  # ------------------ #
-  # Running automake.  #
-  # ------------------ #
-
-  # Assumes that there is a Makefile.am in the topmost directory.
-  if (!-f 'Makefile.am')
-    {
-      verbose "$configure_ac: not using Automake";
-    }
-  else
-    {
-      # We should always run automake, and let it decide whether it shall
-      # update the file or not.  In fact, the effect of `$force' is already
-      # included in `$automake' via `--no-force'.
-      xsystem ($automake);
-    }
-
-
   # ------------------- #
   # Rerunning aclocal.  #
   # ------------------- #
@@ -466,6 +448,24 @@
 
 
   # ------------------ #
+  # Running automake.  #
+  # ------------------ #
+
+  # Assumes that there is a Makefile.am in the topmost directory.
+  if (!-f 'Makefile.am')
+    {
+      verbose "$configure_ac: not using Automake";
+    }
+  else
+    {
+      # We should always run automake, and let it decide whether it shall
+      # update the file or not.  In fact, the effect of `$force' is already
+      # included in `$automake' via `--no-force'.
+      xsystem ($automake);
+    }
+
+
+  # ------------------ #
   # Running autoconf.  #
   # ------------------ #
 

-- 
Andreas Schwab, SuSE Labs, address@hidden
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."