Topic: Compiling BitcoinD 0.9.2 for Centos 6.5 (final) (Read 1385 times)
Make it into what?
dont give up it easily done. You need to edit the makefile.unix
Bah. I give up. Zapping CentOS 6.5 (no more yum 
)
Installing Debian ("I can't breathe!!") 7.1
MD
) Installing Debian ("I can't breathe!!") 7.1
MD
And that didn't work either.
I can't figure out how to get the Bitcoin compiler to reference the OpenSSL libs that I got.
Can anyone help?
I can't figure out how to get the Bitcoin compiler to reference the OpenSSL libs that I got.
Can anyone help?
I did LDD and it shows that it still pulled from the OS even though I specified a different package location.
Well, I just did a make install on the new OpenSSL and I'll recompile from that.
MD
Well, I just did a make install on the new OpenSSL and I'll recompile from that.
MD
This error means that the OpenSSL you're linking against doesn't have support for ECC. Some distributions do this because of (perceived) patent issues.
If you compile OpenSSL yourself it should work, but make sure that it is actually using your compiled version of that library at run time, and not picking the OS one.
(ie, either use something like LD_LIBRARY_PATH to point it at the right .so, check with `ldd` command, or link OpenSSL statically so it's not an issue)
If you compile OpenSSL yourself it should work, but make sure that it is actually using your compiled version of that library at run time, and not picking the OS one.
(ie, either use something like LD_LIBRARY_PATH to point it at the right .so, check with `ldd` command, or link OpenSSL statically so it's not an issue)
I did do this exact thing -- edited as per this (where it pointed to the actual paths):
Code:
export OPENSSL_INCLUDE_PATH="/usr/local/ssl/include"
export OPENSSL_LIB_PATH="/usr/local/ssl/lib"
export OPENSSL_LIB_PATH="/usr/local/ssl/lib"
I will check LDD -- I actually didn't do that yet.
MD
This error means that the OpenSSL you're linking against doesn't have support for ECC. Some distributions do this because of (perceived) patent issues.
If you compile OpenSSL yourself it should work, but make sure that it is actually using your compiled version of that library at run time, and not picking the OS one.
(ie, either use something like LD_LIBRARY_PATH to point it at the right .so, check with `ldd` command, or link OpenSSL statically so it's not an issue)
If you compile OpenSSL yourself it should work, but make sure that it is actually using your compiled version of that library at run time, and not picking the OS one.
(ie, either use something like LD_LIBRARY_PATH to point it at the right .so, check with `ldd` command, or link OpenSSL statically so it's not an issue)
Lot of people use centos and debian for servers. I believe that I can help you if you are using debian for servers.
I've tried it a lot of ways and I simply can't get past one more error message...
bitcoind: key.cpp:134:::CECKey::CECKey(): Assertion `pkey != __null' failed.
I'm using OpenSSL 1.0.1f and I've done a ./config enable-ec enable-ecdsa enable-ecdh prior to the make on that
Can anyone lend some guidance on how to properly compile BitcoinD for CentOS 6.5?
bitcoind: key.cpp:134:
I'm using OpenSSL 1.0.1f and I've done a ./config enable-ec enable-ecdsa enable-ecdh prior to the make on that
Can anyone lend some guidance on how to properly compile BitcoinD for CentOS 6.5?
Jump to: