Re: checking for libraries that link but do not run

[Ralf Wildenhues]

* Ralf Wildenhues wrote on Thu, Oct 08, 2009 at 07:27:47AM CEST:
> But apart from that, I also think that Autoconf should make it easier
> for the developer to state:
> 
> - At this point I require the compile command to be able to link an
>   executable (AC_PROG_{CC,..} don't do this consistently enough)

This one was wrong.  The defaults should probably be the other way
round: the AC_PROG_* macros should require to be able to link, and
packages which want it differently (such as GCC, binutils, Libtool)
should announce that through some macro.  The thing I'm not yet sure
of is whether this will work smoothly with AC_PROG_LIBTOOL.

> - At this point I require being able to run an executable (in non-
>   cross-compile mode).