%% Pavel Roskin <[EMAIL PROTECTED]> writes:
pr> 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.
pr> Very evil idea. Somebody who have never cross-compiled (but still
pr> a good programmer) will decide for you, the guru of
pr> cross-compilation, whether you can cross-compile his program or
pr> not.
Yes, but cross-compilation typically requires _some_ support or at least
thought in configure.in. If the person writing the configure.in doesn't
want to or hasn't added that support, then probably he/she isn't too
interested in hearing from people trying to use it! This differs, IMO,
from the config.cache thing where that's a completely separate question.
The theory is anyone who is guru enough to take out the macro is guru
enough to deal with the resulting chaos and probably errors in building,
and anyone who doesn't know enough to remove the macro shouldn't be
doing it.
That was my thinking, anyway.
However, it doesn't matter to me at all whether this part or the next part:
>> 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.
is enacted; the important thing is the newbies are protected (and thus
my inbox is protected from them :).
--
-------------------------------------------------------------------------------
Paul D. Smith <[EMAIL PROTECTED]> Network Management Development
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
These are my opinions---Nortel Networks takes no responsibility for them.
