Hello, Alexandre!

> > What does --cross add that we don't already have?
> 
> The only point I see about it is that it *forces* configure to think
> it's being cross-compiled.  So, even if an executable appears to run,
> GCC won't assume it's not cross-compiling.

Not only that.

My idea was that the absence of "--cross" should make "configure" stop
with an error and give you a chance to fix your system or try harder with
"--cross" if the compiler produces non-execuable files.

If autodetection doesn't behave how users expect it should (in both ways,
by the way), we should give them a choice instead of further confusing
them with canonical names and other magic words.

Regards,
Pavel Roskin

Reply via email to