Lucas Nussbaum <lucas@xxxxxxxxxx> writes: > See http://qa-logs.debian.net/2020/09/26.ac270/ Hi, Kronosnet Debian maintainer here. I looked into the build problem, and arrived at this example: AC_PREREQ([2.63]) AC_INIT([foo],1.0,[devel@xxxxxxxxxxx]) AC_CONFIG_MACRO_DIR([m4]) AX_PROG_CC_FOR_BUILD AC_OUTPUT Using #serial 18 of AX_PROG_CC_FOR_BUILD from the Autoconf Archive https://www.gnu.org/software/autoconf-archive/ax_prog_cc_for_build.html the generated configure script succeeds under Autoconf 2.69 but fails under Autoconf 2.69c like checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether the compiler supports GNU C... yes checking whether gcc accepts -g... yes checking for gcc option to enable C11 features... none needed checking how to run the C preprocessor... gcc -E checking build system type... x86_64-pc-linux-gnu checking whether the C compiler works... no configure: error: in `/build/kronosnet-pMvMXW/for_build': configure: error: C compiler cannot create executables See `config.log' for more details The details reveal a compilation attempt without a compiler: configure:3420: checking whether the C compiler works configure:3442: conftest.c >&5 ./configure: line 3444: conftest.c: command not found The AX_PROC_CC_FOR_BUILD macro is fairly simple, I think you'll immediately see the compatibility problem (unlike me). I hope this is useful; please Cc me if I can be of some help. -- Regards, Feri
