This seems unlikely but just in case … did you press Ctrl-C during the opam install?
That exit code -1073741510 (the lowers bits are 0xC000013A) usually means STATUS_CONTROL_C_EXIT: “{Application Exit by CTRL+C} The application terminated as a result of a CTRL+C.”
Hey, yes that is the case. Sorry for not pointing that out. I have interrupted the program because I had been waiting on it for like 2 hours already. I thought that it shouldn’t take that long. After I interrupted the program, this error showed up (after the [ERROR] user interrupt).
It’s surprising from your previous post that it’s ended up using the tar in system32 and not the Cygwin one. Can I check what your opam config report is giving (still MSYS2-based) but also the output from opam option sys-pkg-manager-cmd?
Hmm, I’m struggling to reproduce it. I had been wondering whether it was a difference between Windows 10 and Windows 11’s tar (the one in Windows 11 has compiled-in bzip2 support, the one in Windows 10 calls out to bzip2 instead, which needs to be supplied separately). However, this seemed to be working on my Windows 10 system. What does where bzip2 give you (I’m expecting C:\msys64\usr\bin\bzip2)? It’s worth saying that it will be slow - the Dune tarball contains ~7000 files and it gets extracted several times for the different package builds (that’s something we hope to improve) - but it shouldn’t be taking 2 hours!