summaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2010-09-27 11:20:12 -0400
committerNick Mathewson <nickm@torproject.org>2010-09-27 11:20:12 -0400
commit2579d827ab5e840561fb293f42a7147b8ba78efe (patch)
tree0444c981634b6d1ec33aa0c6f3fd4942acef186f /changes
parent83f9667fe804a627ce84f433bca84e7f61264fd7 (diff)
downloadtor-2579d827ab5e840561fb293f42a7147b8ba78efe.tar.gz
tor-2579d827ab5e840561fb293f42a7147b8ba78efe.zip
Use autoreconf, not autoconf&&automake&&etc in autogen.sh
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.
Diffstat (limited to 'changes')
-rw-r--r--changes/autoreconf5
1 files changed, 5 insertions, 0 deletions
diff --git a/changes/autoreconf b/changes/autoreconf
new file mode 100644
index 0000000000..c08cc7a376
--- /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.
+