Hi, Some uninformed reactions.
Dmitrijs Ledkovs wrote: > --- a/ostable > +++ b/ostable > @@ -31,3 +31,4 @@ bsd-openbsd openbsd openbsd[^-]* > sysv-solaris solaris solaris[^-]* > uclibceabi-uclinux uclinux-uclibceabi uclinux[^-]*-uclibceabi > uclibc-uclinux uclinux-uclibc uclinux[^-]*(-uclibc.*)? > +w64-mingw32 w64-mingw32 mingw32[^-]* The ABI part (e.g., sysv-, gnu-, or bsd-) describes instruction set variant and conventions for function calls, dynamic linking, and program startup. That last part often depends on libc. In this case, it is mingw-w64, abbreviated as w64, I suppose. Why not plain "mingw" --- are programs built with mingw32 unable to safely use DLLs built with mingw64, for example? The OS part (e.g., -linux) represents the kernel and maybe the userland tools. Should it be "winnt"? What versions of Windows are being targeted? Functionally, the effect is to determine DEB_HOST_ARCH DEB_HOST_ARCH_OS DEB_HOST_GNU_TYPE for use by debian/rules when building packages targeted at that system. (I know you realize this, just reminding myself!) > Gcc 4.5 and higher recognises -w64-mingw32 So the value in the "GNU name" column is correct. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org