Maybe we could add option like --enable-debug to build winpthreads with debug features? In this case we can assume the regular library build with complete toolchain.
I remember a few months ago there was something on the list about detecting whether libgcc is available when building winpthreads, but iirc it didn't end up in anything. This sounds like a good thing to do; we just need to figure out the best way to do it. - Kirill Makurin ________________________________ From: Martin Storsj? <[email protected]> Sent: Thursday, October 2, 2025 10:12 PM To: [email protected] <[email protected]> Subject: Re: [Mingw-w64-public] [V2] winpthreads: integrate tests from tests_pthread directory with Automake On Thu, 2 Oct 2025, Kirill Makurin wrote: > Also, I see usage of AC_NO_EXECUTABLES in winpthreads' configure.ac. I > do not fully understand its effect, can it affect this link test? Yes, potentially. Winpthreads can be built in a number of different scenarios. The regular one is where it is built like any user library, when you already have a fully working toolchain. In this case, configure time link tests should work (but I'm not sure if AC_NO_EXECUTABLES makes them not do that). But for GCC setups where libgcc/libstdc++ uses winpthreads as threading backend, winpthreads needs to be built before you have built libgcc, so any regular linking test will fail, as the toolchain is yet incomplete. That's why the build of winpthreads tries to supply a small dummy libgcc which is used during the build instead. // Martin _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
