On Sonntag, 1. Oktober 2017 22:10:17 CEST Bruno Haible wrote: > Tim Rühsen wrote: > > FYI, it builds with this sequence > > PREFIX=x86_64-w64-mingw32 > > export CC=$PREFIX-gcc-win32 > > export CXX=$PREFIX-g++-win32 > > export CPP=$PREFIX-cpp-win32 > > export RANLIB=$PREFIX-ranlib > > ./configure --build=x86_64-pc-linux-gnu --host=$PREFIX > > > > I have not found any docs about this > > My preferred recipe for building GNU packages for mingw is here: > http://git.savannah.gnu.org/gitweb/?p=gettext.git;a=blob_plain;f=README.wind > ows > > The major difference between my recipe and yours is that you are building on > Linux. How do you execute the built binaries? If with WINE, how do you make > sure you are not observing a WINE bug?
That's a good point. I am not sure. So I now installed CygWin in a Win10 VM - and at least there the hangs are gone there. But I am also not sure, if CygWin uses the underlying Windows API or not. Have to make some more experiments. @Gisle Maybe you can test branch 'tmp-pthread-abstraction' of Wget2 on Windows ? To check if the test suite in tests/ (sometimes) hangs or not. Regards, Tim
signature.asc
Description: This is a digitally signed message part.