Debian GNU/Linux autoconf marked 2.13 is *not* 2.13--fix uploaded.
Due to a small bug in either autoconf or my build scripts, depending
on how you look at it, the Debian GNU/Linux autoconf package version
2.13-1 is actually not autoconf 2.13, it is an older CVS version. I
have now uploaded a new, fixed version 2.13-2. It should be available
on all Debian mirrors within a day or two.
This message is directed to autoconf@gnu.org since I've seen a number
of bugs reported against 2.13 sent to this list, when in fact they are
probably applicable to only my Debian package, not to the upstream
sources. Those who have reported bugs against upstream autoconf by
considering only the Debian package should check whether the bugs are
still exhibited in 2.13-2.
Now, for the bug: the distclean target in the Makefile for autoconf
doesn't delete the .m4f files, which means that blindly applying the
diffs made against an older version of autoconf to a newer version
won't necessarily rebuild the .m4f files, which means that an older
version of autoconf will essentially be installed. This is what
happened to me.
Suggested fix:
--- autoconf-2.13/Makefile.in~ Tue Jan 5 08:27:16 1999
+++ autoconf-2.13/Makefile.in Wed Jan 20 18:52:25 1999
@@ -206,7 +206,7 @@
rm -f *.ev *.evs *.ov *.ovs *.cv *.cvs *.ma *.mas
distclean maintainer-clean::
- rm -f Makefile config.status config.cache config.log
+ rm -f $(M4FROZEN) Makefile config.status config.cache config.log
TAGS:
etags ${srcdir}/*.m4 ${srcdir}/*.sh ${srcdir}/[a-z]*.in ${srcdir}/*.texi
Reply to: