----- Original Message ----- > On Mon, Oct 21, 2013 at 9:19 AM, Kai Tietz wrote: > > Hello, > > > > Once again ... We already discussed this issue some time ago directly, > > Earnie. And just by repeating and spreading this nonsense over and over > > again, it doesn't make it right. > > > > I am not going to debate the issue.
Right, I don't debate this anymore too. > > > > So instead, we should change the use of *-*-mingw32* to *-*-mingw* instead. > > Well, we could agree on that even the name *mingw* is something wrong, > > and should something more host-specific as host-part of triplet. But > > well, this is a different discussion. > > Both -mingw32 and mingw64 are to stay. It's not that I don't agree > with you; it is a decision that was not made by me but I support. Again, I am talking about the triplet, not the short-cut in config.guess. mingw32 needs to stay by historic reason for now. To introduce now mingw64 as host-part of 64-bit triplet-name is plain wrong and has to be removed if you already introduced it. By whom was this decision made, if not by you (or your co-maintainer of mingw.org Keith)? So it is you, and nobody else. Stop this hiding behind somebody else not existing. > -- > Earnie > -- https://sites.google.com/site/earnieboyd > Kai _______________________________________________ config-patches mailing list config-patches@gnu.org https://lists.gnu.org/mailman/listinfo/config-patches
