[sr #110397] autoconf 2.70: autotest.m4 error

Update of sr#110397 (group autoconf): Status: Need Info => Not Autoconf Open/Closed:Open => Closed ___ Follow-up Comment #18: We decided to

[sr #110397] autoconf 2.70: autotest.m4 error

Follow-up Comment #17, sr #110397 (project autoconf): I looked into this again, and it seems the issue really is with the old version of m4 that Apple provides. It seems that it can be fixed in autoconf/autom4te, but I'm not sure how much you're willing to support old versions of m4. Details

[sr #110397] autoconf 2.70: autotest.m4 error

Follow-up Comment #16, sr #110397 (project autoconf): I ran into this too, and installing GNU m4 1.4.18 before configuring autoconf did fix it. ___ Reply to this item at:

[sr #110397] autoconf 2.70: autotest.m4 error

Follow-up Comment #15, sr #110397 (project autoconf): Oh, I guess "unknown channel" is coming direct from autom4te, not m4. Sorry. That makes it even more mysterious that you get that error and we don't, since I doubt anything in that Perl code is system-dependent.

[sr #110397] autoconf 2.70: autotest.m4 error

Follow-up Comment #14, sr #110397 (project autoconf): Did you try with current GNU m4 (1.4.18) in the sandbox? 1.4.6 is ancient. When I see the mysterious m4 message "unknown channel", I have to keep wondering about m4 being the issue. When I run configure in automake-1.4.3 against 2.70, I also

[sr #110397] autoconf 2.70: autotest.m4 error

Follow-up Comment #13, sr #110397 (project autoconf): Your new test works: $ cat conftest.ac AC_INIT([test], [1]) AC_USG AC_OUTPUT $ autoconf -o /dev/null conftest.ac conftest.ac:2: warning: The macro `AC_USG' is obsolete. conftest.ac:2: You should run autoupdate.

[sr #110397] autoconf 2.70: autotest.m4 error

Follow-up Comment #12, sr #110397 (project autoconf): First off, yes, automake should change its test to read something like AC_INIT([smoketest], [1]) AC_OUTPUT (Calling `AC_INIT` with no arguments is also deprecated.) However, something else is wrong as well -- I have a bad feeling that

[sr #110397] autoconf 2.70: autotest.m4 error

Follow-up Comment #11, sr #110397 (project autoconf): Re. GNU m4, Apple has: $ /usr/bin/m4 --version GNU M4 1.4.6 Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A

[sr #110397] autoconf 2.70: autotest.m4 error

Follow-up Comment #10, sr #110397 (project autoconf): No, sorry, I was mistaken. I concluded incorrectly that GNU m4 fixed it when everything worked fine on my local machine. When I made GNU m4 available to a sandboxed build environment, it stopped working. There seems to have been something

[sr #110397] autoconf 2.70: autotest.m4 error

Follow-up Comment #8, sr #110397 (project autoconf): Thanks, that seems to have worked. Any idea what the problem might be? ___ Reply to this item at:

[sr #110397] autoconf 2.70: autotest.m4 error

Follow-up Comment #7, sr #110397 (project autoconf): Looking at comment #6, the only idea that comes to mind is to try installing GNU m4 and see if that works around the problem. ___ Reply to this item at:

[sr #110397] autoconf 2.70: autotest.m4 error

Follow-up Comment #6, sr #110397 (project autoconf): Without patch, outside of homebrew, installing automake 1.16.3 with autoconf 2.70 fails: rmeur /tmp/autoconf-2.70 $ ./configure --prefix=/tmp checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is

[sr #110397] autoconf 2.70: autotest.m4 error

Follow-up Comment #5, sr #110397 (project autoconf): Yes, of course. That makes sense. I'll need to look into finding you a machine for remote shell access. However, the build scripts for automake and autoconf are very simple. For automake, it (essentially) runs these commands in the build

[sr #110397] autoconf 2.70: autotest.m4 error

Follow-up Comment #4, sr #110397 (project autoconf): The aclocal command is part of automake; you need existing installed copies of both autoconf and automake to run autoreconf -iv on either autoconf or automake. It's kinda the same thing as needing a C compiler already before you can build gcc.

[sr #110397] autoconf 2.70: autotest.m4 error

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:

[sr #110397] autoconf 2.70: autotest.m4 error

Follow-up Comment #2, sr #110397 (project autoconf): Thanks for the quick response. Here are the autoconf and automake logs from the CI node running macOS 11: https://www.dropbox.com/s/ts1nx36buk3x7a8/logs.tar.gz?dl=1 The logs look similar on the nodes running 10.14 and 10.15, but let me know if

[sr #110397] autoconf 2.70: autotest.m4 error

Update of sr #110397 (project autoconf): Status:None => Need Info ___ Follow-up Comment #1: Thanks for the bug report. It looks like the smoke-test code in your Homebrew recipe was

[sr #110397] autoconf 2.70: autotest.m4 error

URL: Summary: autoconf 2.70: autotest.m4 error Project: Autoconf Submitted by: None Submitted on: Tue 08 Dec 2020 11:09:23 PM UTC Category: None Priority: 5 -