That said, I can't really speak for the Debian Autoconf package. If it
derives from an upstream tarball, it should not need autoconf at build
time at all. If it wishes to use an installed autoconf, it should do
fine with 2.59.
Hope this helps a bit. (And please report back problems!)
Yeah, it's the debian build settings causing the problem, and the
dependency, not something inherent in the autoconf tarball. When
compiling automatically (bypassing the dependency check with
'dpkg-buildpackage -d') it fails during the build stage with:
make[1]: Entering directory
`/tmp/builds/backports/autoconf/autoconf-2.59.cvs.2006.06.05'
cd . && /bin/sh
/tmp/builds/backports/autoconf/autoconf-2.59.cvs.2006.06.05/config/missing
--run autoconf
configure.ac:150: error: possibly undefined macro: AC_PROG_GREP
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:152: error: possibly undefined macro: AC_PROG_SED
The cause of this error appears to be the 'configure-stamp' section of
debian/rules, where it runs aclocal-1.9 and automake-1.9. If I take
out those commands, it builds without errors.
I don't know the significance of buidling with vs. without those
settings, so maybe there are situations where it's not safe to just
remove them, but it seems to work OK for my purposes. If it is always
safe, maybe 'rules' can be changed, and the dependency on a previous
autoconf installation can be removed.
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
