|
From: <sv...@va...> - 2011-10-22 10:44:27
|
Author: bart
Date: 2011-10-22 11:39:43 +0100 (Sat, 22 Oct 2011)
New Revision: 12195
Log:
autogen.sh: Use autoreconf as recommended in the autoconf manual
Modified:
trunk/autogen.sh
Modified: trunk/autogen.sh
===================================================================
--- trunk/autogen.sh 2011-10-22 09:55:37 UTC (rev 12194)
+++ trunk/autogen.sh 2011-10-22 10:39:43 UTC (rev 12195)
@@ -1,17 +1,3 @@
#!/bin/sh
-run ()
-{
- echo "running: $*"
- eval $*
-
- if test $? != 0 ; then
- echo "error: while running '$*'"
- exit 1
- fi
-}
-
-run aclocal
-run autoheader
-run automake -a
-run autoconf
+autoreconf -ivf
|
|
From: Florian K. <br...@ac...> - 2011-10-22 14:18:06
|
On 10/22/2011 06:39 AM, sv...@va... wrote: > Author: bart > Date: 2011-10-22 11:39:43 +0100 (Sat, 22 Oct 2011) > New Revision: 12195 > > Log: > autogen.sh: Use autoreconf as recommended in the autoconf manual > It may be recommended but it isn't creating confidence: Checked out revision 12197. florian@ds9:/tmp> cd valgrind/ florian@ds9:/tmp/valgrind> ./autogen.sh Can't exec "libtoolize": No such file or directory at /usr/bin/autoreconf line 196. Use of uninitialized value in pattern match (m//) at /usr/bin/autoreconf line 196. autoreconf: Entering directory `.' autoreconf: configure.in: not using Gettext ...... I have: automake (GNU automake) 1.11.1 autoconf (GNU Autoconf) 2.67 on Ubuntu 10.10 Running configure succeeds and "make" seems to work as well. Remind me why these changes to the build system were necessary. Florian |