Re: Not-really-cross-compilation issues

[akim]

On Sat, Jan 20, 2001 at 12:22:58AM +0100, Peter Eisentraut wrote:
> I've created a simple shared library that I placed at a non-standard
> location for illustration purposes.  Imagine I want to configure a package
> to link against that library:
> 
> $ cat configure.in
> AC_INIT(.)
> 
> AC_PROG_CC
> 
> AC_OUTPUT
> 
> # With Autoconf 2.13:
> 
> $ LIBS='-L/tmp/obscure -ltest' ./configure
> creating cache ./config.cache
> checking for gcc... gcc
> checking whether the C compiler (gcc  ) works... yes
> checking whether the C compiler (gcc  ) is a cross-compiler... yes
> checking whether we are using GNU C... yes
> checking whether gcc accepts -g... yes
> updating cache ./config.cache
> creating ./config.status
> 
> (everything okay)
> 
> # With Autoconf 2.50-to-be:
> 
> $ LIBS='-L/tmp/obscure -ltest' ./configure
> checking for gcc... gcc
> checking whether the C compiler works... configure: error: cannot run C 
> compiled programs.
> To enable cross compilation, use `--host'.

Indeed...

Could you try see what happened?  For instance, what does that config.log
contain?