RE: OBJ and EXE and cross-compilation (Was: AC_OBJEXT again)

[Bernard Dautrevaux]

> -----Original Message-----
> From: Akim Demaille [mailto:address@hidden
> Sent: Wednesday, December 13, 2000 1:43 PM
> To: Mo DeJong
> Cc: address@hidden
> Subject: Re: OBJ and EXE and cross-compilation (Was: AC_OBJEXT again)
> 
> 
> >>>>> "Mo" == Mo DeJong <address@hidden> writes:
> 
> Mo> But would this still work if I wanted to compile with the mingw
> Mo> compiler under Cygwin? The mingw native compiler is also named
> Mo> gcc, so what --host triple would I need to pass to the configure
> Mo> script? It seems like I would need to pass something for the
> Mo> --host argument, otherwise the configure script would not think it
> Mo> was a cross compile. Is this even a cross compile? Well sort
> Mo> of. (ugh)
> 
> The name of the C compiler is tied to $host.  Sure it tries $host-gcc
> etc., but you can set $host on the one hand, and CC on the other.  So
> I don't think there are any problems here.
> 
> Mo> If I did not pass a host triple, would the configure script detect
> Mo> Cygwin even though CC was set to the mingw compiler? That seems
> Mo> like the logical thing to do if we only use uname. Problem is, if
> Mo> configure sets a bunch of Cygwin #defines and then tries to exec
> Mo> the mingw compiler, all hell will break loose.
> 
> As long as $host != $build, there is cross compilation.  We no longer
> depend upon the compiler to test cross compilation situations.
> 

And thus YES you MUST pass --host in this case, as this IS
cross-compilation; in fact I ALWAYS pass --host and --build in all cases as
I use a script to call $srcdir/configure that detect the host and build
names from where I am building :-)

        Bernard

--------------------------------------------
Bernard Dautrevaux
Microprocess Ingenierie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel:    +33 (0) 1 47 68 80 80
Fax:    +33 (0) 1 47 88 97 85
e-mail: address@hidden
                address@hidden
--------------------------------------------