On 13 December 2010 23:21, Jonathan Nieder <jrnie...@gmail.com> wrote: > Dmitrijs Ledkovs wrote: > >> 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. > > That answers my main question. Then I suppose: > >> 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 > > mingw32-winnt > mingw64-winnt > mingw32-msys > mingw64-msys > mingw32-cygwin > mingw64-cygwin >
----8<---- MSYS is a collection of GNU utilities such as bash, make, gawk and grep to allow building of applications and programs which depend on traditionally UNIX tools to be present. It is intended to supplement MinGW and the deficiencies of the cmd shell. ----8<---- So msys is just a meta-package which runs on mingwXX-winnt. I like: mingw32-winnt - mingw.org based, Windows native port mingw64-winnt - mingw-w64 based, Windows native port mingw32-cygwin - mingw.org based toolchain for/with cygwin port mingw64-cygwin - mingw-w64 based toolchain for/with cygwin port All four of the both multipled by available cpu's resulting in these GNU triplets mingw32-winnt - <cpu>-pc-mingw32 mingw64-winnt - <cpu>-w64-mingw32 mingw32-cygwin - <cpu>-pc-cygwin mingw64-cygwin - <cpu>-w64-cygwin > (Obviously I am not attached to the names, just trying to figure > out which targets need distinct Debian names for compatibility.) > All four of the above triplets make sense and are "in the wild out there not packaged in Debian" > Presumably at the moment you're be working on mingw64-winnt? > Yes. For i386 and amd64 Debian cpu's. >> 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. > > Ah, interesting. > > Thanks again. Others wiser than I am can presumably take it from > here. > Shall I provide an updated patch against dpkg? With regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
