On Fri, Aug 10, 2001 at 01:34:08PM -0500, Michael Heldebrant wrote: > On 10 Aug 2001 18:24:57 +0100, James Green wrote: > > [EMAIL PROTECTED]:~$ autoconf --version > > Autoconf version 2.13 > > > > At which various 'configure' scripts are bailing asking for 2.50 or > > above. It seems autoconf2.13 installs /usr/bin/autoconf-wrapper that > > looks as if it tries to tell which version the configure script is > > intended for use with, and points it in the right direction. > > > > Except it doesn't. I'm now unable to build software using autoconf, so > > stuff like zapping (my tv tuner) is growing old. > > > > Anyone know why this is happening? Can I assume that mving the > > autoconf-2.50 binary to /usr/bin/autoconf will fix this matter? If not, > > what will. And what's happening about a full resolution on this problem? > > Have you taken a look at this blurb in the 2.13 thingy in dselect? > > This package provides compatibility wrappers for autoconf, autoheader, > and autoreconf that attempt to automatically choose which version of > Autoconf to use, based on some simple heuristics. For information on > these heuristics or how to force use of a particular Autoconf version, > see /usr/share/doc/autoconf2.13/README.Debian.gz.
Specifically, AC_PREREQ(2.50) in the configure.in should do, and that (or something similar) is correct if the package's configure.in requires autoconf 2.50. -- Colin Watson [EMAIL PROTECTED]
