On Fri, Mar 13, 2015 at 6:54 PM, s7r <s...@sky-ip.org> wrote: > What is curious is that it still sates version : 90300, regardless I
realpath bitcoind [absolute path] /<absolute_path_to>/bitcoind -\? | head -1 [bitcoind version] ldd /<absolute_path_to>/bitcoind | grep libssl strings <that libssl> | grep OpenSSL [ssl version] If fully static, strings /.../bitcoind | grep OpenSSL [ssl version] > everything is up to date, all dependencies are installed and Without seeing your complete command history from download through build to exec, these are ambiguous phrases. Brief read of the net says bitcoind 0.10x with openssl 1.0.1l should work. Could be paths to bitcoind/libssl/libcrypto, or mixed up/old versions. Or the bit of net I read is wrong. You probably don't want to subject bitcoind to the randomness of packaging systems. Static build in a private directory should fix that. Today the static part may be something like: CPPFLAGS=-static LDFLAGS=-static ./configure ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ bitcoin-list mailing list bitcoin-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-list