Follow-up Comment #3, sr #110397 (project autoconf):
Sorry, I just noticed you mentioning the automake configure script needing to
be regenerated with the new autoconf. That's not done in the CI run, which
just calls the configure script immediately. I just tried to run it locally
instead:
autoreconf: export WARNINGS=
autoreconf: Entering directory '.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force
Can't exec "aclocal": No such file or directory at
/usr/local/Cellar/autoconf/2.70/share/autoconf/Autom4te/FileUtils.pm line
274.
autoreconf: error: aclocal failed with exit status: 2
This is the error from running `autoreconf --verbose` in the build directory
for automake. Adding `--install` or `--force` flags don't seem to help, but
I'll admit to having no idea what I'm doing here.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110397>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
