CC: mingw-w64 mailing list I'm asking to add mingw32-w64 tripplet and os to dpkg. Please suggest / improve how you would like to have debian or tripplet be called. We are settled that GNU tripplet will be <cpu>-w64-mingw32 =)
On 12 December 2010 01:30, Jonathan Nieder <jrnie...@gmail.com> wrote: > Hi, > > Some uninformed reactions. > Thank you for shedding some more lights of what ABI/OS parts should mean! > 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 ABI part describes instruction set variant etc" "That last part often depends on libc" ----8<---- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=360587#35 On Thu, Sep 06, 2007 at 12:08:10PM -0500, Tony J. White wrote: > > Why was the name 'i586-mingw32msvc' choosen? To indicate the target binaries for this build use the msvcrt runtime. ----8<---- There are currently two free implementations of msvcrt: mingw.org and mingw-w64. Programs built with mingw32 *unable* to safely use DLLs built with mingw64 there are subtle differences in implementations. The biggest one is that mingw-w64 is 32/64 bit aware. > 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? > winnt is okish, but see further. mingw-w64 compiles for Windows XP and it has additional headers for compatability and features of Vista and 7. We have one ABI (windows-like) and then for OS parts it could be "native" - msvcrt or "unix-like" - cygwin. For free kernel options we have ReactOS and linux+wine. For msvcrt we have options of using mingw and w64. So maybe something like this: Debian name: ms-msvcrt ms-cygwin And then it's up to Debian maintainers which msvcrt implementation (analogy with libc) to use - mingw.org or w64 (this one). We can package both to test and compare and find bugs, etc. The "original" now zomby debian-wi...@l.d.o was aiming to create ms-cygwin port. > 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
