I get the following output when I run "./autogen.sh" in the root of a classpath CVS checkout. Am I doing something wrong? This has happened several times in a row, even after I updated my aclocal.m4 by running "aclocal -I ." (Not that I should have to, since autogen does it for me, but there is that warning from libtoolize.)
--Steve Augart ------- Output Follows ------ libtoolize (GNU libtool) 1.4.3 libtoolize: minimum version required: 1.4.2 autoconf (GNU Autoconf) 2.59 autoconf: minimum version required: 2.59 autoheader (GNU Autoconf) 2.59 autoheader: minimum version required: 2.59 automake (GNU automake) 1.7.7 automake: minimum version required: 1.7.0 aclocal (GNU automake) 1.7.7 aclocal: minimum version required: 1.7.0 libtoolize ... You should update your `aclocal.m4' by running aclocal. aclocal ... autoheader ... automake ... native/fdlibm/Makefile.am:1: Libtool library used but `LIBTOOL' is undefined native/fdlibm/Makefile.am:1: native/fdlibm/Makefile.am:1: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' native/fdlibm/Makefile.am:1: to `configure.ac' and run `aclocal' and `autoconf' again. native/jni/classpath/Makefile.am:1: Libtool library used but `LIBTOOL' is undefined native/jni/classpath/Makefile.am:1: native/jni/classpath/Makefile.am:1: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' native/jni/classpath/Makefile.am:1: to `configure.ac' and run `aclocal' and `autoconf' again. native/jni/gtk-peer/Makefile.am:1: Libtool library used but `LIBTOOL' is undefined native/jni/gtk-peer/Makefile.am:1: native/jni/gtk-peer/Makefile.am:1: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' native/jni/gtk-peer/Makefile.am:1: to `configure.ac' and run `aclocal' and `autoconf' again. native/jni/java-awt/Makefile.am:1: Libtool library used but `LIBTOOL' is undefined native/jni/java-awt/Makefile.am:1: native/jni/java-awt/Makefile.am:1: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' native/jni/java-awt/Makefile.am:1: to `configure.ac' and run `aclocal' and `autoconf' again. native/jni/java-io/Makefile.am:1: Libtool library used but `LIBTOOL' is undefined native/jni/java-io/Makefile.am:1: native/jni/java-io/Makefile.am:1: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' native/jni/java-io/Makefile.am:1: to `configure.ac' and run `aclocal' and `autoconf' again. native/jni/java-lang/Makefile.am:1: Libtool library used but `LIBTOOL' is undefined native/jni/java-lang/Makefile.am:1: native/jni/java-lang/Makefile.am:1: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' native/jni/java-lang/Makefile.am:1: to `configure.ac' and run `aclocal' and `autoconf' again. native/jni/java-net/Makefile.am:1: Libtool library used but `LIBTOOL' is undefined native/jni/java-net/Makefile.am:1: native/jni/java-net/Makefile.am:1: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' native/jni/java-net/Makefile.am:1: to `configure.ac' and run `aclocal' and `autoconf' again. native/jni/java-nio/Makefile.am:1: Libtool library used but `LIBTOOL' is undefined native/jni/java-nio/Makefile.am:1: native/jni/java-nio/Makefile.am:1: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' native/jni/java-nio/Makefile.am:1: to `configure.ac' and run `aclocal' and `autoconf' again. native/jni/java-util/Makefile.am:1: Libtool library used but `LIBTOOL' is undefined native/jni/java-util/Makefile.am:1: native/jni/java-util/Makefile.am:1: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' native/jni/java-util/Makefile.am:1: to `configure.ac' and run `aclocal' and `autoconf' again. Compilation exited abnormally with code 1 at Wed May 12 06:43:49 _______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
