On Thu, Feb 5, 2026, at 6:37 AM, Jose E. Marchesi wrote: > [Sam James found this issue while packaging godcc for Gentoo: > https://packages.gentoo.org/packages/dev-util/godcc. Would be nice if > we could have this fixed in autoconf 2.73.] > > The AC_PROG_A68 macro should honor the A68FLAGS set by the user at > configure time.
Thanks for the patch. I have merged a revised version as commit <https://cgit.git.savannah.gnu.org/cgit/autoconf.git/commit/?id=26c15054083ae5e185689301dc1e3733657f518b>. The revisions address the issues with ac_test_A68FLAGS which were pointed out downthread, in a simpler way; this macro doesn't actually *use* A68FLAGS at any point, so we don't need to save and restore the user value, we just need to set a default value, which the shell has a built-in (albeit cryptic) construct for. The revisions also drastically simplify the code for finding the compiler executable. This appears to have been copied from AC_PROG_CC, which has much nastier compatibility headaches; a single AC_CHECK_TOOLS invocation should be plenty good enough for a new toolchain like GNU A68. > Note that a similar fix may be needed in AC_PROG_GO. I have not > fixed that one because it may be intentional there? (unlikely, but > just in case.) I don't believe this was intentional and I've also patched this one in <https://cgit.git.savannah.gnu.org/cgit/autoconf.git/commit/?id=cc481d03b142e6609bedfa0b90c07d5b00f87085>. I'd appreciate it if folks already familiar with GNU Algol68 and/or Go would test these changes. (Note: It has to be gccgo. We don't support Google's go compiler, because its command line interface is not cc-compatible.) I don't speak either language and it'd probably take me all day just to set up the toolchains. > Signed-off-by: Jose E. Marchesi <[email protected]> FYI, this project doesn't use Signed-off-by. zw
