On Tue, 2004-09-07 at 16:03, Alexandre Duret-Lutz wrote: > >>> "Stephen" == Stephen torri <[EMAIL PROTECTED]> writes: > > [...] > > Stephen> bash-2.05b$ autoconf --version > Stephen> autoconf (GNU Autoconf) 2.59 > Stephen> Written by David J. MacKenzie and Akim Demaille. > > The config.log you sent shows the output of Autoconf 2.13. If > you are running the above example and the failing configure from > the very same shell session, it might be caused by a shell > configuration that mistakenly reset PATH for non-login shells.
The problem is with the version of autoconf installed. I am on a Gentoo system which they provide autoconf-2.13 and autoconf-2.59. Here are the criteria that will cause autoconf-2.59 to be used over 2.13: # - 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.13' # -or- # - `configure' is already present and was generated by autoconf greater than # '2.13' # -or- # - `Makefile.in' was generated by automake-1.6 or superior, which # specifically needs autoconf-2.59 # What ever reason for the wrong autoconf to be used when there is a configure.ac present I don't know. When I did "export WANT_AUTOCONF=2.5" the check passed. Stephen -- Email: [EMAIL PROTECTED]
