As was clarified to me by GCC devs (who pointed me to [1]), there is no mingw64 anywhere. The autotools target triplet is named *-w64-mingw32 and the project is named mingw-w64, so naming the package mingw64-runtime in Gentoo is just confusing. In addition, mingw-runtime was apparently renamed to mingwrt by upstream. So that maybe that should be changed as well. [1] http://sourceforge.net/apps/trac/mingw-w64/wiki/Answer%20Multilib%20Toolchain Reproducible: Always
no documentation says the tuple is "mingw64". crossdev handles the tuples that binutils/etc.. uses: x86_64-*-mingw* & *-w64-mingw* the upstream package name has long been "mingwrt" or "mingw-rt" where "rt" stands for "runtime". so the Gentoo ebuild used "mingw-runtime". i can't say that i even think "mingw-w64" is a better name than "mingw64-runtime". certainly changing the $PN at this point would be a pita since it's been encoded in various places (eclasses, crossdev, installed packages, etc...). since i don't see any real gain, and i certainly see downsides, WONTFIXing ...
i've updated crossdev so that if you ask for 'mingw64', it'll expand it into the right tuple automatically (x86_64-w64-mingw32) http://git.overlays.gentoo.org/gitweb/?p=proj/crossdev.git;a=commitdiff;h=02eae3ddd3e6088e65b98f66e73b24663c65e888
(In reply to comment #2) > i've updated crossdev so that if you ask for 'mingw64', it'll expand it into > the right tuple automatically (x86_64-w64-mingw32) Thanks, that is great! (Do you do the same thing for mingw32?)
P.S: * dev-util/mingw64-runtime-2.0.7 seems to create x86 libraries in addition to x86-64 ones. Is that intended? * And also it installs the 64bit libraries into lib/ instead of lib64/. Is that intended, too?
(In reply to comment #3) "mingw32" is a valid tuple ;) (In reply to comment #4) i think you meant to post to the version bump bug, not this one
