Hi Adam, On Mon, Apr 11, 2011 at 07:14:32PM +0200, Adam Borowski wrote: > (Reporting while the package is still stuck in NEW, sorry if it becomes > misplaced. Reportbug claims the maintainer is ok, not sure about > the BTS.)
Everything seems to have worked OK, although the BTS is slightly confused. If you want to you can reassign the bug to mingw-w64 which is in the archive already! > The compiler triplets seem to be wrong: > > * i686-w64-mingw32 has "w64" in name, yet executables it produces work > perfectly on 32 bit systems. I even checked on an ancient 32 bit only > machine to be 100% sure. > > To add confusion, other builds call it i586-mingw32msvc or just mingw32. > > * x86_64-w64-mingw32 has "w32", but its executables are 64 bit. This is how the upstream project (MinGW-w64) goes about things. There are at least two reasons: * The "w64" part is to identify the triplet as corresponding to MinGW-w64 as opposed to MinGW. * The "mingw32" part is maintained so that existing configure scripts will still work (in particular, configure scripts written with MinGW in mind will work with MinGW-w64). The MinGW-w64 project itself targets both 32- and 64-bit Windows. The target is identified by its CPU (i[3456]86 for 32-bit, x86_64 for 64-bit); the API isn't supposed to change much... The "other builds" calling it i586-mingw32msvc or i586-mingw32 are builds of MinGW, not MinGW-w64 (and MinGW-w64 is a separate project from MinGW, not MinGW's 64-bit variant). The triplets are those officially recognised by the various GNU projects involved as well (binutils and gcc mainly), and are already used in other distributions (notably Fedora which has a whole bunch of MinGW-w64 packages) and by lots of downstream software (see the list for instance on http://mingw-w64.sf.net). > Not to mention the whole package being named *-mingw-w64 while its existing > counterparts have "-w" less (-mingw32), but that'd be probably too much work > to change at this point. This inconsistency has nowhere as big potential > for confusion as -w64- in the 32 bit compiler. The mingw32 packages are based on MinGW, not MinGW-w64. The old MinGW-w64 package using MinGW's binutils and gcc was supposed to be a short-term hack and was eventually abandoned. The long term plan is actually to get rid of the mingw32 packages, once the packages which build-depend on them have been updated to build with mingw-w64 instead (including for 32-bit Windows). All this has been discussed with both upstream and MinGW's maintainer in Debian. I realise it's not ideal, but many users of MinGW-w64 are already used to this way of doing things... Regards, and thanks for your interest, Stephen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
