#297 conftest.c: command not found

[Fabio Rossi]

# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
enabling gui support
disabling gpsim socket interface
checking whether make supports the include directive... yes (GNU style)
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 whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for popt.h... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for gtk+-2.0 >= 2.24 glib-2.0 >= 2.26 gthread-2.0... yes
linking with gtk-2.24.33
checking for readline/readline.h... yes
./configure: line 5948: conftest.c: command not found

configure.ac has a small error, wi_LIB_READLINE macro needs $CPP which is not set until AC_PROG_CXX is called, it is sufficient to move the call to wi_LIB_READLINE after the AC_PROG_xxx lines

[Roy Rankin]

I do not see either of your configure.ac issues in Fedora, but also your patches also work fine in Fedora. So your bug should be fixed in svn 2647