the autoconf package installs both autoconf 2.13 and 2.59, and uses the /usr/lib/autoconf/ac-wrapper.pl wrapper to determine which one to call. the comments in the beginning of the wrapper script say the following: # - defaults to autoconf-2.13 # - runs autoconf-2.59 if it exists and... # - envvar WANT_AUTOCONF is set to `2.5' # -or- # - configure.ac is present # -or- # - `configure.in' contains AC_PREREQ and the value's 3 first letters # are stringwise greater than '2.1' # -or- # - `configure' is already present and was generated by autoconf greater than # '2.1' # -or- # - `Makefile.in' was generated by automake-1.6 or superior, which # specifically needs autoconf-2.59 but, even if AC_PREREQ is set to 2.5 or 2.59 in a configure.ac file, the wrapper calls autoheader 2.13 if configure.ac is explicitly specified as a command line argument. Reproducible: Always Steps to Reproduce: 1. create a minimal configure.ac file, and put it into a seperate directory than the current one. put AC_PREREQ(2.59) into this configure.ac 2. invoke autoheader with the configure.ac as an argument 3. see that autoheader 2.13 is invoked, instead of 2.59 Actual Results: $ autoheader etc/configure.ac FATAL ERROR: Autoconf version 2.59 or higher is required for this script /* config.h.in. Generated automatically from etc/configure.ac by autoheader. */ Expected Results: calling autoheader-2.59 explicitly runs the correct verson: $ autoheader-2.59 etc/configure.ac and of course there is a reason I would want to run autoheader-2.59, as it actually generates the header file in my case, whereas 2.13 doesn't. here's the configure.ac file I used for testing: AC_INIT(Hello, 1.0) AC_PREREQ(2.59) AC_CONFIG_SRCDIR(src/main.cxx) AC_CONFIG_HEADERS(src/configure.h) AC_PROG_CXX() AC_CONFIG_FILES(Makefile) AC_OUTPUT() and the directory structure is as follows: . |-- Makefile.in |-- etc | `-- configure.ac `-- src |-- configure.h.in `-- main.cxx
This is stopping me from emerging kde and arts. I have tried replacing /usr/lib/autoconf/ac-wrapper.pl as referenced in a bug that I can no longer find. Have also tried re-emerging autoconf Basic steps to reproduce: root@betty.net[/usr/bin] # auto[tab] auto.ftpfs autoconf-2.59 autoheader-2.59 automake-1.4 autool autoreconf-2.57 autoscan-2.59 autozen auto.sshfs autocutsel autom4te automake-1.5 autopoint autoreconf-2.59 autoupdate autoconf autoheader autom4te-2.57 automake-1.6 autopopups autoscan autoupdate-2.13 autoconf-2.13 autoheader-2.13 autom4te-2.59 automake-1.7 autoreconf autoscan-2.13 autoupdate-2.57 autoconf-2.57 autoheader-2.57 automake automake-1.8 autoreconf-2.13 autoscan-2.57 autoupdate-2.59 root@betty.net[/usr/bin] # autoheader /usr/bin/m4: configure.in: No such file or directory root@betty.net[/usr/bin] # autoheader --version Autoconf version 2.13 root@betty.net[/usr/bin] #
fixed in autoconf-2.59-r6+
