On 08/24/2018 05:59 PM, Jeffrey Walton wrote:
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
Nope, that's not how you do it. You NEED the AM_INIT_AUTOMAKE() line,
just not necessarily the higher version number requirement within the line.
I'm thinking more along the lines of:
sed -i '/AM_INIT_AUTOMAKE/ s/\b[0-9.]*\b//'
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.
Insulting the tools and/or the people that are trying to help you
resolve your issues isn't going to resolve the issue.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
https://lists.gnu.org/mailman/listinfo/autoconf
