bug#45180: closed (Building automake 1.16.3 with autoconf 2.70 fails)

[GNU bug Tracking System]

Your message dated Sun, 13 Dec 2020 15:46:22 -0700
with message-id <202012132246.0BDMkMQX019341@freefriends.org>
and subject line Re: bug#45180: Building automake 1.16.3 with autoconf 2.70 
fails
has caused the debbugs.gnu.org bug report #45180,
regarding Building automake 1.16.3 with autoconf 2.70 fails
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
45180: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=45180
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> Building automake 1.16.3 with autoconf 2.70 fails
>
>
>
>
> Date: 
>
> Fri, 11 Dec 2020 13:45:07 +0100
>
>
>
>
> On macOS (all supported versions from 10.14 to 11.0), building automake 1.16.3 
> with the newly released autoconf 2.70 fails. The error is the following:
>
> configure:3113: checking whether autoconf works
> configure:3121: cd conftest && autoconf -o /dev/null conftest.ac
> unknown channel m4trace: -1- _m4_warn(syntax, AC_OUTPUT was never used, )
> at /tmp/share/autoconf/Autom4te/Channels.pm line 631.
>         Autom4te::Channels::msg("m4trace: -1- _m4_warn(syntax, AC_OUTPUT was 
> never used, )\x{a}", undef, undef, "partial", 0) called at /tmp/bin/autom4te 
> line 1073
> configure:3124: $? = 1
> configure:3133: result: no
> configure:3136: error: The installed version of autoconf does not work.
>
>
> See the full build output at https://savannah.gnu.org/support/index.php?110397 
> I do not know whether this is a autoconf or automake issue, but the two tools 
> should work together, shouldn’t they?
>
> FX
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#45180: Building automake 1.16.3 with autoconf 2.70 fails
>
>
>
>
> Date: 
>
> Sun, 13 Dec 2020 15:46:22 -0700
>
>
>
>
>     See my full build output in comment #6 at
>     https://savannah.gnu.org/support/index.php?110397#comment6
>
> I'm glad GNU m4 worked, per our follow-up discussion there.
>
> I'm going to close the bug here. It makes more sense for any more
> follow-up to happen in the savannah ticket, since there's already
> lots more information there. --best, karl.
>
>
>
> --- End Message ---