On Sunday 29 May 2011, Stefano Lattarini wrote:
> [Adding automake-patches]
>
> On Saturday 28 May 2011, Graham Reitz wrote:
> > Hi Stefano,
> >
> > Did you have a chance to take a look at the config and test logs?
> > (they are attached)
> >
> > I've been trying to figure it out without much success.
> >
> I think I've found the problem: the `aclocal.in' and `automake.in'
> "templates" (from which the `aclocal' and `automake' scripts are
> generated) fail to honour the AUTOCONF and AUTOM4TE defined at
> configure time, and simply use literal "autom4te" and "autoconf"
> instead. This is a real bug in Automake's own build system, and
> is still present in the latest developement version. The attached
> two-patches series (for maint) should fix it. Graham, do you mind
> trying if it solves your problem? I will push the patches shortly
> if there is no objection.
>
> Thanks,
> Stefano
>
I've now pushed the patches after tweaking the ChangeLog entries.
Here are the updated ChangeLog entries:
2011-05-29 Stefano Lattarini <stefano.lattar...@gmail.com>
build: the user can override AUTOM4TE, AUTORECONF and AUTOUPDATE too
Our build system allows the user to override AUTOCONF and AUTOHEADER
at configure time, and honours these overrides in our testsuite.
But it didn't do the same with AUTOM4TE, AUTORECONF and AUTOUPDATE.
This change fixes that inconsistency.
* configure.ac (am_AUTOM4TE, am_AUTOUPDATE, am_AUTORECONF): New
AC_SUBSTitutions. Update comments.
* tests/defs.in ($AUTOUPDATE): Default to `@am_AUTOUPDATE@' now.
($AUTOM4TE): New variable, defaulting to `@am_AUTOM4TE@'.
($AUTORECONF): New variable, defaulting to `@am_AUTORECONF@'.
* doc/Makefile.am ($(srcdir)/amhello-1.0.tar.gz): Update.
2011-05-29 Stefano Lattarini <stefano.lattar...@gmail.com>
automake, aclocal: honour configure-time AUTOCONF and AUTOM4TE
Currently, the Automake's own configure script allow definition
of AUTOCONF and AUTOM4TE, expected to point respectively to an
autoconf and autom4te programs. But while these definitions are
honoured in the Automake's build systems and test suite, they
were *not* honoured in the generated `automake' and `aclocal'
scripts. This behaviour, apart from being wrong in that it does
not allow the user enough freedom in choosing his tools, also
caused inconsistencies in the test suite, brining to spurious
failures.
Problem reported by Graham Reitz on the automake list; see thread:
<http://lists.gnu.org/archive/html/automake/2011-05/msg00022.html>
* automake.in ($traces): Use `@am_AUTOCONF', not simply `autoconf'.
* aclocal.in ($traces): Use `@am_AUTOM4TE', not simply `autom4te'.
* Makefile.am (do_subst): Substitute also `@am_AUTOCONF' and
`@am_AUTOM4TE'.
* NEWS: Update.
* THANKS: Update.
Regards,
Stefano
