On 2017/4/9 8:12, Edward Diener wrote: > 1) if mcfgthread replaces the mingw-64/gcc-6.3 threading library when used. It takes the place of winpthreads completely.
> 2) if it replaces the mingw-64/gcc-6.3 threading library even when I had > installed mingw-64/gcc-6.3 with posix threading support as opposed to > Windows threading support. It is not possible. You have to rebuild GCC libraries, which in turn requires rebuilding GCC itself. (You don't have to have Clang to build libcxx, but sadly this isn't the case on GCC.) The file `libpthread.a` is not provided. That is to say, if you are building GCC while you don't have winpthreads you have to put an empty file in `@prefix@/lib`. This file can be safely deleted once you get your GCC working. There is usually no other problem, unless you are linking against a 3rd party library that has `libgcc` and `libstdc++` linked statically. > 3) if I replace the functionality in the mingw-64/gcc-6.3 threading > library with mcfgthread by merely adding the mcfgthread DLL import > library when compiling with mingw-64/gcc-6.3, and making sure the > mcfgthread DLL library is in my Windows PATH. Correct. -- Best regards, LH_Mouse ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
