On Wed, Feb 23, 2005 at 10:58:27AM +0100, Jeroen van Wolffelaar wrote: > On Wed, Feb 16, 2005 at 03:53:49PM +1000, Adam Conrad wrote: > > Martin Orr said: > > > > > > Could you change configure.in to have AC_PREREQ(2.50) at the top? > > > > That's my planned fix, yes. :) > > That doesn't sound to me like the correct solution to this bug, though. > The problem is that autoconf gets invoked without making sure the right > autoconf is invoked. > > Either running autoconf is needed, then somehow autconf2.5 needs to be > invoked,
That is exactly what AC_PREREQ(2.50) does. apache2 already Build-Depends on autoconf which in sid and sarge means 2.50 (actually 2.59) - although perhaps there should be a versioned Build-Depends. The problem occurs if you install autoconf2.13 at the same time (which was what I had but didn't realise). It diverts /usr/bin/autoconf to autoconf2.50 and replaces it with a script which does some heuristics to try to guess which version is required - and most often selects 2.13 (as in the case of apache2). One of the checks is to look for an AC_PREREQ line so by adding that, the wrapper will indeed run autoconf2.50. -- Martin Orr Linux Administrator, Methodist College Belfast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]