# letting version tracking do its work tags 243618 - experimental + moreinfo quit
Hi, Long ago, Scott James Remnant wrote[1]: > On Wed, 2004-04-14 at 02:37, Paul Brossier wrote: >> example bad behavior follows: >> $ ./bootstrap >> + rm -f aclocal.m4 >> + aclocal >> + libtoolize --force --copy > > aclocal now needs to be run after libtoolize. I vaguely remember pain surrounding this change. [...] >> configure.ac:52: error: possibly undefined macro: AC_LIBTOOL_DLOPEN >> If this token and others are legitimate, please use m4_pattern_allow. >> See the Autoconf documentation. >> configure.ac:53: error: possibly undefined macro: AC_DISABLE_STATIC >> configure.ac:54: error: possibly undefined macro: AC_PROG_LIBTOOL > > Which causes this to fail. > >> the same script runs fine using versions and 1.6-0+1.5a-2 Can you still reproduce this? If not, do you remember approximately when or how it was fixed? Sorry for the trouble, and hope that helps, Jonathan [1] http://bugs.debian.org/243618 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org