-----BEGIN PGP SIGNED MESSAGE-----
> On Thu, Nov 12, 2009 at 3:11 PM, Ralf Wildenhues <Ralf.Wildenhues@xxxxxx>
>> Why, BTW, does x86_64-w64-mingw32 have "32" in the name?
> Win64 still uses the Win32 API. There was a big discussion about that
> when creating the new triplet, which ultimately ended with "The real
> answer is to not have a number at the end at all, but 32 is more
> correct than 64." This is why pretty much every test looks for
> ...-mingw* instead of mingw32. We'd like to eventually remove it.
> Ideally, we'd go a step further and really utilize the vendor triplet.
> We would do something like i686-mingw-windows < for a traditional
> compiler from mingw.org. This will be bike shedded to death, though,
> unfortunately. But it'd be nice.
Yeah, before we proceed any further some of this fundamental facts should be
decided. I know such discussions are always difficult. But it doesn't make any
sense to fight each other.
I know the historical debate between the mingw.org team and the team which is
pushing *w64-mingw32. And I have to say that all of them did a great job in
their project. But also it's true that on both sides mistakes were made.
I hope for a constructive discussion and creative solutions!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----