%% Ossama Othman <[EMAIL PROTECTED]> writes:
oo> Right. I'm sure that this issue has already been beaten to death,
oo> but I haven't been a bit distracted these past few weeks. Have
oo> any steps been taken to address the faults with the detection
oo> code, at least to improve it, and despite the fact that is
oo> impossible to correctly detect a cross-compiler?
I'm not sure what could be done. Currently, the code assumes that if
the program links but can't run, it must be cross-compiled.
Given a perfect installation of the native compiler, that's a reasonable
assumption. Back when almost ever UNIX came with a compiler
pre-installed (presumably correctly), it probably worked fairly well.
Unfortunately, these days most proprietary UNIX vendors no longer ship
compilers, and people wanting to just build FVWM or something have to
install one themselves; often these people are not technically
sophisticated and things go bad. The result is that it is far more
common for a non-runnable binary to be the result of a bad installation
than a cross-compiling environment.
Personally, I can't think of any way to improve this, save asking the
user to tell us exactly what he wants.
--
-------------------------------------------------------------------------------
Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at:
http://www.gnu.org http://www.ultranet.com/~pauld/gmake/
"Please remain calm...I may be mad, but I am a professional." --Mad Scientist
