Re: Is this a bug in autoconf? (patch included)

[Alexandre Oliva]

On Apr 25, 2000, Ian Lance Taylor <[EMAIL PROTECTED]> wrote:

>    From: Alexandre Oliva <[EMAIL PROTECTED]>
>    Date: 25 Apr 2000 18:31:45 -0300

>    On Apr 25, 2000, Ian Lance Taylor <[EMAIL PROTECTED]> wrote:

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

> I believe we should change autoconf so that if $build and $host are
> different, it assumes that it is being cross-compiled.

> Given that, what does --cross add?

I don't see any benefits.  But I'd see some reason for a --no-cross if
build and host happen to be different but the compiler in use is not a
real cross compiler.  Think of sparc64->sparc32 builds, for example.

-- 
Alexandre Oliva    Enjoy Guaranį, see http://www.ic.unicamp.br/~oliva/
Cygnus Solutions, a Red Hat company        aoliva@{redhat, cygnus}.com
Free Software Developer and Evangelist    CS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org}   Write to mailing lists, not to me