Mike Simons - 2001-07-31

Logged In: YES
user_id=285084

versions for special magic make making crap...

libtoolize (GNU libtool) 1.4
aclocal (GNU automake) 1.4-p5
autoheader (GNU Autoconf) 2.52
automake (GNU automake) 1.4-p5
autoconf (GNU Autoconf) 2.52

there appears to be some bad interactions between libtool
and autoconf... in the libtool stuff I see things like
libtool-1.4/NEWS:
====
New in 1.3d: 2001-04-02; CVS version 1.3c, Libtool team:
* ltconfig is no more. Generation of libtool happens
directly from the configure file.
====
and in aclocal.m4 (which appears to be part of autoconf)
===
# Actually configure libtool. ac_aux_dir is where
install-sh is found.
CC="$CC" CFLAGS="$CFLAGS" CPPFLAGS="$CPPFLAGS" \
LD="$LD" LDFLAGS="$LDFLAGS" LIBS="$LIBS" \
LN_S="$LN_S" NM="$NM" RANLIB="$RANLIB" \
DLLTOOL="$DLLTOOL" AS="$AS" OBJDUMP="$OBJDUMP" \
${CONFIG_SHELL-/bin/sh} $ac_aux_dir/ltconfig --no-reexec \
$libtool_flags --no-verify $ac_aux_dir/ltmain.sh $lt_target \
|| AC_MSG_ERROR([libtool configure failed])
[... then later ...]
LIBTOOL='$(SHELL) $(top_builddir)/libtool'
AC_SUBST(LIBTOOL)dnl

====

I found that if the first block is commented out, and if
LIBTOOL= is changed to LIBTOOL=libtool, then a few minor
changes to the configure.in (to not use libtool instead of
./libtool) and it finally builds some Makefiles which mostly
work.