Date: Tue, 25 Apr 2000 19:59:51 -0400 (EDT)
   From: Pavel Roskin <[EMAIL PROTECTED]>

   > > 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.

I assume you mean in the absence of an explicit --build or --host
option.

   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.

If I ask for a cross-compile, I don't see why I have to add --cross
too.  I said what I want.

Ian

Reply via email to