[OpenAFS-devel] Minimum autoconf version

[Jeffrey Hutzelman]

On Friday, July 01, 2005 02:28:13 PM -0400 Ken Hornstein 
<kenh@cmf.nrl.navy.mil> wrote:

> What's the minimum autoconf version that we are using with OpenAFS?
>
> I ask because in the autoconf glue I did for aklog, I started getting
> complaints because I used AC_ARG_VAR and apparantly some people out
> there (you know who you are) were still using autoconf 2.13, which
> didn't have it.  I'm wondering if we can all agree on what the minimum
> autoconf version is and standardize on it with AC_PREREQ (I'm hoping it
> will be something newer than 2.13).  I also noticed that the configure
> behavior is different for some macros between 2.13 and later versions
> (specifically, the tests done when doing AC_CHECK_HEADERS seems to be
> more comprehensive in later version of autoconf), and that complicated
> things when I was writing the autoconf tests; that's why I'd like to
> get the autoconf version mess straightened out.


To date, we have tried to keep the configure.in compatible with both 2.13 
and 2.5x.  I've been building with whatever 2.5x I have lying around for 
some time, and generally don't have problems, even with 2.59.

Part of the reason for this is that release tarballs, which contain 
pre-generated configure scripts, are constructed on a machine on which the 
only installed autoconf is 2.13.  This could probably be changed, if the 
gatekeepers decided to move forward and start requiring new autoconf, but 
until it is, tossing in 2.5x dependencies will break the release process.

-- Jeff