Hello, Paul!
> 1) Cross-compilation should be turned off unless some autoconf macro
> exists that says "this package is cross-compiler capable". If the
> compiler can't run the compiler test program and this special macro
> isn't present, configuration should fail right there.
Very evil idea. Somebody who have never cross-compiled (but still a good
programmer) will decide for you, the guru of cross-compilation, whether
you can cross-compile his program or not.
> Or, alternatively, there could be a command-line option which
> enables cross-compilation checking. The error above could be
> something like "Couldn't find a working compiler (if you want to
> cross-compile, add --enable-cross-compilation to the configure
> command)" or whatever.
It is much better. I remember me proposing something like that a couple of
years ago :-)
> 2) If you've already tested for C and that decided it _wasn't_
> cross-compiling, then you test for C++ and it decides you _are_
> cross-compiling, that should be a fatal error right there, too.
Agreed. Either you are cross-compiling or you are not. Period.
Regards,
Pavel Roskin
