compiling failures - missing DLLs?

[caissist]

Hello Adam,
compiling with msys2 ucrt64 14.2.0 r1 64-bit is succesfully.
Running the binary on same comp (Win11 Prof 64-bit) where having been compiled is possible without any problems.
But running same binary on a different comp (Win10 Prof 64-bit) in console mode leads to a failure message on missing dlls as following:
libgcc_s_seh-1.dll
libstdc++-6.dll
libwinpthread-1.dll

I searched for those DLLs, downloaded them and registered them by regsrv32 but I failed. Wrong DLL versions?
Do you have the correct DLL versions for Win10 at hand?

Another try: compiling with MinGW 19.0 without problems.
Calling UCI command in console mode is possible, but when running the binary under a GUI on a chess server the engine is stuck?!
MinGW Distro - nuwen.net: MinGW 19.0
https://nuwen.net/mingw.html
* binutils 2.41
* GCC 13.2.0
* mingw-w64 11.0.1
*
What do you think? Thank you.

[Adam-Kulju]

I have never tested with mingw and have always compiled with clang++. If you don't have that compiler on hand, does downloading one of the executables from the releases page work? Or I can compile an executable for you?

For transferring executables to a different machine with a different Windows version, the dll versions are probably different and that's the reason why the executable doesn't work. I don't know about the correct DLL versions for windows 10, I don't do much work with that stuff.

Sorry I can't help you with this, is there any particular reason why you can't download 3.1 or build from source using clang++?

[caissist]

I have never tested with mingw and have always compiled with clang++

msys2 mingw is a widely known and respected serious alternative. And I compiled with the current version.
A such situation I experienced a first time over decades.

Or I can compile an executable for you?

Thank you !

does downloading one of the executables from the releases page work?

There is just a single binary version 3.1?! And that I've used so far as you know, too.
Now I compiled successfully. I solved that missing dll failure by putting those dlls into the engine's folder.