How about writing our own autoconf in Pike and drop autoconf totally? All versions of autoconf seems to have issues.
As long as there is a ./configure generated...
/ Mirar
Previous text:
2003-05-04 13:20: Subject: Re: --localdir backwards compatibility
|The renaming of --localdir to --prepend-include is annoying when |trying to keep a configure.in compatible between 2.13 and more modern |versions. To make it less painful, I patched in some backwards |compatibility to my local version of autoconf-2.57. Seems to work fine |for me.
Please, drop 2.13, as it is too buggy, and trying to maintain compatibility with it is the worse that could happen to your scripts.
| |--- autoconf.in-original Tue Nov 5 08:16:59 2002 |+++ autoconf.in Tue Apr 15 14:23:43 2003 |@@ -194,7 +194,9 @@ | --prepend-include=* | -B?* | \ | --warnings=* | -W?* ) | AUTOM4TE="$AUTOM4TE $1"; shift ;; |- |+ --localdir=* ) |+ AUTOM4TE="$AUTOM4TE --prepend-include=${1:11}" ; shift ;;
I do not believe this would be portable anyway.
/ Brevbäraren