[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 #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 #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 #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: