UPDATED - Linux x64 bins for those having libcrypto and GLIBCXX_3.4.11 troubles

View Satoshi only

External link

This is mostly for those having troubles on fedora with newer openssl than the binaries on the front page of the site were built with.

Please try these or compile yourself using these instructions:


Works on Slackware64 13.1.
No dice on my Gentoo system. I get the following.

$ bitcoin
bitcoin: /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/ version `GLIBCXX_3.4.11' not found (required by bitcoin)

and then

$ ldd bitcoind
./bitcoind: /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/ version `GLIBCXX_3.4.11' not found (required by ./bitcoind) =>  (0x00007fffc9bff000) => /lib/ (0x00007ffeefbe1000) => /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.4/ (0x00007ffeef8d3000) => /lib/ (0x00007ffeef64e000) => /lib/ (0x00007ffeef437000) => /lib/ (0x00007ffeef21a000) => /lib/ (0x00007ffeeeea4000)
   /lib64/ (0x00007ffeefde5000)

This file isn't statically linked. I'm only trying to use it because my gentoo system is in a bad state and will take some time to get upgraded to build the source code.

Anyways, thought I'd send a bug report
I get the same:
`GLIBCXX_3.4.11' not found
on Debian.

The libg++ is not as new as the one bitcoind was compiled with, and the newer one is not available in stable.
Is it possible to statically link the c++ library?  If it is possible, is it something that is an acceptable practice or does it cause problems?  Maybe just include the library with the program?  When I said static I was only referring to openssl Smiley
We don't even specify linking glibcxx_3.4.11, so gcc must automatically link it behind the scenes.  There's probably a compiler switch that would tell it to static link it.  I'm not sure what the licensing issues would be.  Typically, compiler stuff is fully redistributable.