-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Statically link to libstdc++ helps many users on various linux distributions. #5596
Comments
see #4026 for some previous talk about this, there are also some other aspects of why static linking on linux is not recommended. https://gcc.gnu.org/onlinedocs/libstdc++/manual/abi.html |
Out of curiosity what is stockfish currently linking to on linux? On windows ldd output is:
|
windows has static linking, due to the nature of libraries generally missing there |
On linux package maintainers do a fairly good job at tracking the most recent releases. https://packages.debian.org/search?keywords=stockfish |
(Just FOUND) How to solve: https://askubuntu.com/questions/1393285/how-to-install-glibcxx-3-4-29-on-ubuntu-20-04
Then check if the version appears in the list: |
This is basic knowledge, also credit you because you took someone elses answer lol? |
Annoying part about these old libc versions is they keep the compiler version old. And that potentially makes the final binary slower, and on clang makes the build slower. GCC didn't have big build speed improvements if I remember correctly. |
iirc from testing different compilers older versions were actually better at optimizations |
Describe the issue
After downloading stockfish 17 avx2 on my debian bullseye system, it won't run, because:
Expected behavior
If you opt for statically linked standard libraries (on linux), this would not happen and the program would be usable out of the box on many more systems.
Steps to reproduce
Anything else?
The compiler option you might want to use to fix this is:
-static-libstdc++
.Operating system
All
Stockfish version
Stockfish 17 as of the time of this issue post.
The text was updated successfully, but these errors were encountered: