> It is not autoconf's problem when someone writes a configure.ac that wrongly
> claims to use too-new of a version of automake. But if you don't think the
> package is actually relying on a feature that only that newer automake
> provided, you are welcome to edit configure.ac and change the
> AM_INIT_AUTOMAKE() line to list a lower version number, rerun autoreconf,
> and see if it completes successfully.
OK, let's get rid of these useless checks whose only purpose is to
stop someone from accomplishing their task at hand.
sed -i '/AM_INIT_AUTOMAKE/d' configure.ac
And what a surprise:
$ autoreconf -f -i
Can't exec "autopoint": No such file or directory at
/usr/share/autoconf/Autom4te/FileUtils.pm line 345.
autoreconf: failed to run autopoint: No such file or directory
Autotools does everything in its freaking powers to stop someone from
accomplishing their task.
> Or, actually install newer versions of the autotools.
Lol... That put milk up my nose. I've tried to install newer versions
and they have never worked right. The admins on the GCC compile farm
tried the same and the shit does not work right. Claiming someone can
upgrade these tools is a joke.
Jeff
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
https://lists.gnu.org/mailman/listinfo/autoconf
