Re: [avr-libc-dev] Are there any autoconf/automake experts around?

[Wojtek Kaniewski]

Joerg Wunsch wrote:
> > The other approach is to add CFLAGS="-c" before and CFLAGS="" after
> > AC_PROG_CC, to make autoconf think that it links an executable, when
> > in fact it doesn't. But that's just an ugly hack.
>
> ...and it didn't work.

It works for me. Without modified CFLAGS, configure outputs:

   checking for C compiler default output file name... configure: error:
   C compiler cannot create executables
   See `config.log' for more details.

config.log states:

   configure:2208: checking for C compiler default output file name
   configure:2211: avr-gcc    conftest.c  >&5
   /usr/lib/gcc/avr/3.4.4/../../../../avr/bin/ld: crts8515.o: No such
   file: No such file or directory
   configure:2214: $? = 1

After adding CFLAGS="-c" before AC_PROG_CC, configure says:

   checking for C compiler default output file name... b.out

And config.log:

   configure:2208: checking for C compiler default output file name
   configure:2211: avr-gcc -c   conftest.c  >&5
   configure:2214: $? = 0

Anyway, if AC_NO_EXECUTABLES works fine for you, let's forget this hack.

Regards,
Wojtek