search for: winpthread

...msys2. When I run `./configure` without any parameters and I still see missing pthreads impl. >> >> I have installed mingw64 cross compiler toolchain. Here is the output of pacman I see when searching for pthreads (they are all installed). >> >> mingw64/mingw-w64-x86_64-libwinpthread-git 7.0.0.5480.e14d23be-1 (mingw-w64-x86_64-toolchain) [installed] >> MinGW-w64 winpthreads library >> mingw64/mingw-w64-x86_64-winpthreads-git 7.0.0.5480.e14d23be-1 (mingw-w64-x86_64-toolchain) [installed] >> MinGW-w64 winpthreads library >> msys/mingw-w64-cross-winpt...

.../configure` without any parameters and I still see missing pthreads impl. > >> > >> I have installed mingw64 cross compiler toolchain. Here is the output of pacman I see when searching for pthreads (they are all installed). > >> > >> mingw64/mingw-w64-x86_64-libwinpthread-git 7.0.0.5480.e14d23be-1 (mingw-w64-x86_64-toolchain) [installed] > >> MinGW-w64 winpthreads library > >> mingw64/mingw-w64-x86_64-winpthreads-git 7.0.0.5480.e14d23be-1 (mingw-w64-x86_64-toolchain) [installed] > >> MinGW-w64 winpthreads library > >> msys/m...

Hi, I am trying to compile Libvirt from the source code on windows using msys2 but keep hitting issues while running `./configure`. …. > checking whether C compiler handles -Wno-suggest-attribute=pure… yes > checking whether C compiler handles -Wno-suggest-attribute=const... yes > checking for how to force completely read-only GOT table… > checking for how to avoid indirect lib

...without any parameters and I still see missing pthreads impl. >>>> >>>> I have installed mingw64 cross compiler toolchain. Here is the output of pacman I see when searching for pthreads (they are all installed). >>>> >>>> mingw64/mingw-w64-x86_64-libwinpthread-git 7.0.0.5480.e14d23be-1 (mingw-w64-x86_64-toolchain) [installed] >>>> MinGW-w64 winpthreads library >>>> mingw64/mingw-w64-x86_64-winpthreads-git 7.0.0.5480.e14d23be-1 (mingw-w64-x86_64-toolchain) [installed] >>>> MinGW-w64 winpthreads library >>>&...

...> I am using msys2. When I run `./configure` without any parameters and I still see missing pthreads impl. > > I have installed mingw64 cross compiler toolchain. Here is the output of pacman I see when searching for pthreads (they are all installed). > > mingw64/mingw-w64-x86_64-libwinpthread-git 7.0.0.5480.e14d23be-1 (mingw-w64-x86_64-toolchain) [installed] > MinGW-w64 winpthreads library > mingw64/mingw-w64-x86_64-winpthreads-git 7.0.0.5480.e14d23be-1 (mingw-w64-x86_64-toolchain) [installed] > MinGW-w64 winpthreads library > msys/mingw-w64-cross-winpthreads-git 7.0...

On Windows there are a few 'pthreads' implementation, e.g. pthreads-w32 and winpthreads [https://cran.r-project.org/doc/manuals/r-devel/R-exts.html#Using-pthreads]. We're thinking of giving them a try for the matrixStats package, and basic tests indicates it works, but since Windows pthreads are not used by core R (or?) I've got a little bit worried that we will face overwhel...

...care of completely replicating the current state of the process. > > Kasper > > On Fri, Aug 14, 2015 at 5:00 PM, Henrik Bengtsson < > henrik.bengtsson at ucsf.edu> wrote: > >> On Windows there are a few 'pthreads' implementation, e.g. >> pthreads-w32 and winpthreads >> [ >> https://cran.r-project.org/doc/manuals/r-devel/R-exts.html#Using-pthreads >> ]. >> We're thinking of giving them a try for the matrixStats package, and >> basic tests indicates it works, but since Windows pthreads are not >> used by core R (or?) I...

...aarch64-libpsl 0.21.2-4 mingw-w64-clang-aarch64-libssh2 1.11.0-1 mingw-w64-clang-aarch64-libtasn1 4.19.0-1 mingw-w64-clang-aarch64-libtiff 4.5.1-2 mingw-w64-clang-aarch64-libunistring 1.1-1 mingw-w64-clang-aarch64-libunwind 16.0.5-1 mingw-w64-clang-aarch64-libwebp 1.3.1-1 mingw-w64-clang-aarch64-libwinpthread-git 11.0.0.r107.gd367cc9d7-1 mingw-w64-clang-aarch64-libxml2 2.11.4-2 mingw-w64-clang-aarch64-lld 16.0.5-3 mingw-w64-clang-aarch64-llvm 16.0.5-3 mingw-w64-clang-aarch64-llvm-libs 16.0.5-3 mingw-w64-clang-aarch64-make 4.4-2 mingw-w64-clang-aarch64-mlir 16.0.5-1 mingw-w64-clang-aarch64-nettle 3.9.1-1...

Indeed, mingw and pthreads have C++11 atomics, so building clang (with atomics) should be possible even in cross compilation. I have no idea what is the win from *not* using winpthreads, it is one small DLL file with BSD license. For context (does not matter to mingw as host for buiilding clang but matters for clang running with mingw environment), clang TLS implementation is not same as mingw so atomics do not work for clang+mingw pthreads unless you replace libstdc++ with libc...

..., fork is a system call which takes care of completely replicating the current state of the process. Kasper On Fri, Aug 14, 2015 at 5:00 PM, Henrik Bengtsson <henrik.bengtsson at ucsf.edu > wrote: > On Windows there are a few 'pthreads' implementation, e.g. > pthreads-w32 and winpthreads > [https://cran.r-project.org/doc/manuals/r-devel/R-exts.html#Using-pthreads > ]. > We're thinking of giving them a try for the matrixStats package, and > basic tests indicates it works, but since Windows pthreads are not > used by core R (or?) I've got a little bit worried...

On Tuesday, 27 June 2017 13:55:57 CEST Richard W.M. Jones wrote: > We permit the following constructs in libguestfs code: > > if (guestfs_some_call (g) == -1) { > fprintf (stderr, "failed: error is %s\n", guestfs_last_error (g)); > } > > and: > > guestfs_push_error_handler (g, NULL, NULL); > guestfs_some_call (g); >

AKA: MinGW + win32threads is holding LLVM (and all of its subprojects) back. We need to stop supporting this host platform. I'm aware of essentially 2 reasonably important use cases for supporting MinGW + win32threads: 1) Sane host toolchain on Windows that doesn't require downloading MSVC. (I'm dubious about the value of this one...) 2) Cross-compiling a Windows clang.exe (and

The patches following do indeed allow you to compile nbdkit.exe, but it does not actually work yet. I'm posting this experimental series more as a work in progress and to get feedback. Note this does not require Windows itself to build or test. You can cross-compile it using mingw64-* packages on Fedora or Debian, and test it [spoiler alert: it fails] using Wine. Rich.

Also available here: https://github.com/rwmjones/nbdkit/tree/2020-windows-mingw This is the port to Windows using native Windows APIs (not MSYS or Cygwin). This patch series is at the point where it basically now works. I can run the server with the memory plugin, and access it remotely using guestfish, creating filesystems and so on without any apparent problems. Nevertheless there are many

Also available here: https://github.com/rwmjones/nbdkit/tree/2020-windows-mingw-nolib After a lot of work I have made the port to Windows work without using a separate library. Instead, on Windows only, we build an "import library" (library of stubs) which resolves references to nbdkit_* functions in the main program and fixes up the plugin, basically the first technique outlined in