This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] config.guess: Properly detect the *mingw32 targets


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ralf Wildenhues schrieb:
> * Charles Wilson wrote on Thu, Nov 12, 2009 at 01:54:46PM CET:
>> Rainer Emrich wrote:
>>> for the traditional i686-pc-mingw32 target everything works fine.
>>> The msys uname -s returns MINGW32* and for this case config.guess
>>> unconditionally returns i686-pc-mingw32.
>>>
>>> But now we have two additional targets i686-w64-mingw32 and x86_64-w64-mingw32
>>> which are also build using msys. But config.guess unconditionally returns
>>> i686-pc-mingw32 for msys systems, that's the point. So you always have to
>>> specify --build for this two targets. This is solved by the patch.
>> Given the objections to using the compiler itself to determine the
>> system,
> 
> BTW, you really need to ask Ben about this; I was merely repeating from
> memory, so take with salt.  IIRC invoking the compiler may be
> problematic in some circumstances (and config.guess is used by a lot of
> very different packages).
But if you parse config.guess there are several cases where the compiler is
invoked!

> 
> Why, BTW, does x86_64-w64-mingw32 have "32" in the name?
> 
> Cheers,
> Ralf
> 

Cheers,
Rainer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkr8l60ACgkQoUhjsh59BL7e6ACeLGA147+1ZfO6lqidVX4t1+Zl
T+4AoKaFCpSajMsmd/EnTqupF2mTKRYE
=dZRt
-----END PGP SIGNATURE-----


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]