[or-cvs] [tor/master] Use autoreconf, not autoconf&&automake&&etc in autogen.sh

[nickm@xxxxxxxxxxxxxx]

Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date: Mon, 27 Sep 2010 11:20:12 -0400
Subject: Use autoreconf, not autoconf&&automake&&etc in autogen.sh
Commit: 2579d827ab5e840561fb293f42a7147b8ba78efe

The autoreconf tool deals much better with detecting which tools to
use on your particular platform, handling cases where your
install-sh script gets stable, and lots of other little tricky
issues.

We still fall back to autoconf&&automake&&etc in the case where
"`which autoreconf 2>/dev/null`" says something we can't run.

This is the first change of the 0.2.3.x series.
---
 autogen.sh         |    4 ++++
 changes/autoreconf |    5 +++++
 2 files changed, 9 insertions(+), 0 deletions(-)
 create mode 100644 changes/autoreconf

diff --git a/autogen.sh b/autogen.sh
index eb9395c..0592f16 100755
--- a/autogen.sh
+++ b/autogen.sh
@@ -1,5 +1,9 @@
 #!/bin/sh
 
+if [ -x "`which autoreconf 2>/dev/null`" ] ; then
+  exec autoreconf -ivf
+fi
+
 set -e
 
 # Run this to generate all the initial makefiles, etc.
diff --git a/changes/autoreconf b/changes/autoreconf
new file mode 100644
index 0000000..c08cc7a
--- /dev/null
+++ b/changes/autoreconf
@@ -0,0 +1,5 @@
+  o Minor build changes:
+    - Use autoreconf to launch autoconf, automake, etc from autogen.sh.
+      This is more robust against some of the failure modes associated
+      with running the autotools chain on its own.
+
-- 
1.7.1