On Thu, Jun 21, 2018 at 5:38 PM Andrew J. Schorr <
address@hidden> wrote:
On Thu, Jun 21, 2018 at 11:05:54AM -0400, Andrew J. Schorr wrote:
> I think the real question is why aclocal is being run in the first place. The
> tarball includes a functioning configure script and Makefiles, so it shouldn't
> be necessary to run the autotools again. Are you touching configure.ac?
> The bootstrap.sh script could possibly be useful for freshening the timestamps
> to avoid re-running autotools, but that's not typically necessary when building
> from a tarball.
Ah, OK, I guess you're applying commit bd8a8ad0c258d2db31e420eec81932cf15bf9702
which which patches configure.ac. So that's why it's trying to rebuild the
configure script.
In configure.ac, it says:
AM_INIT_AUTOMAKE([1.15 dist-xz dist-lzip])
According to the automake docs:
VERSION
A version number (e.g., '0.30') can be specified. If Automake is
not newer than the version specified, creation of the 'Makefile.in'
will be suppressed.
I would guess that a newer version of automake, i.e. 1.16 instead of 1.15,
should be OK.
Have you tried running "autoreconf --force -i" before running configure
and make?
I have actually done it after I added 'automake' into builtroot, the build passed. I can see if this works as well without patching the ./configure script to use 1.16... :)