Compilation Issue - make #8706

knoxcard commented at 10:56 PM on September 12, 2016: contributor

Operating System: Debian Jessie OpenSSL Version (latest): OpenSSL_1_0_1t

I am getting the following error when I make compile. libbitcoin_util.a(libbitcoin_util_a-util.o): In function CInit::CInit()': /root/.bitcoin/latest_release/bitcoin-0.13.0/src/util.cpp:147: undefined reference toOPENSSL_init_crypto' collect2: error: ld returned 1 exit status Makefile:3317: recipe for target 'bitcoind' failed make[2]: *** [bitcoind] Error 1 make[2]: Leaving directory '/root/.bitcoin/latest_release/bitcoin-0.13.0/src' Makefile:8338: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/root/.bitcoin/latest_release/bitcoin-0.13.0/src' Makefile:667: recipe for target 'all-recursive' failed make: *** [all-recursive] Error 1

knoxcard commented at 6:35 AM on September 13, 2016: contributor

the above error happens when I run make. Before that, autogen and configure work successfully... http://pastebin.com/18RZPsth

laanwj added the label Build system on Sep 13, 2016

laanwj commented at 9:31 AM on September 13, 2016: member

Looks like OpenSSL header exists but the library is not linked? Can you pastebin the output of:

make V=1

knoxcard commented at 6:07 AM on September 14, 2016: contributor

Sure, here is the paste bin output...

http://pastebin.com/xeTauqNd

knoxcard commented at 6:10 AM on September 14, 2016: contributor

Does this help at all?

http://stackoverflow.com/questions/22269408/linking-challenges-with-gcc-and-crypto-libraries

jonasschnelli commented at 6:24 AM on September 14, 2016: contributor

It looks like it does correctly link against libcrypto. Can you double-check what openssl package you have installed? Could it be that you have or had install one of openssl substitutes (like libreSSL)?

knoxcard commented at 6:31 AM on September 14, 2016: contributor

https://www.openssl.org/docs/man1.1.0/crypto/OPENSSL_config.html

knoxcard commented at 6:32 AM on September 14, 2016: contributor

I have had quite a few OpenSSL installs, my current active install is...

openssl version OpenSSL 1.0.1t 3 May 2016

knoxcard commented at 6:48 AM on September 14, 2016: contributor

I would love to completely remove all other openSSL installs previously made on my server to clear out SSL headers. Never had a problem in the past installing the Bitcoin core, OpenSSL version 1.1.0 has to be the culprit, as it's the only recent change I've made.

knoxcard commented at 9:32 AM on September 14, 2016: contributor

I did not install libreSSL.

knoxcard commented at 4:59 AM on September 15, 2016: contributor

this got it for me! all installed...

[Special thanks to user2084795] http://stackoverflow.com/questions/29477569/use-self-compiled-openssl-to-compile-bitcoin-on-fedora-21

Bitcoin appears to run on an old version of OpenSSL, OpenSSL version: OpenSSL 1.0.2a 19 Mar 2015 , which I found surprising. Wasn't OpenSSL support removed though?

SOLUTION install dependecies export OPENSSL_PREFIX=/usr/local/ssl/ Download and unzip openssl-1.0.2a source code CC='cc -fPIC' ./config --prefix=$OPENSSL_PREFIX make all install_sw Download and unzip bitcoin source code ./autogen.sh ./configure --without-gui CPPFLAGS="-I/usr/local/BerkeleyDB.4.8/include -O2" LDFLAGS="-L/usr/local/BerkeleyDB.4.8/lib" make sudo make install

knoxcard closed this on Sep 15, 2016

knoxcard commented at 4:59 AM on September 15, 2016: contributor

Maybe in the future, during the Bitcoin install phase, prompt the user allowing them to change this openSSL path.

jonasschnelli commented at 6:30 AM on September 15, 2016: contributor

Wasn't OpenSSL support removed though?

It has been removed from the consensus layer, but is still used for the PRNG and the BIP70 stuff in the GUI. The remaining puzzle to remove it from the non-GUI bitcoin-core is the PRNG (there is a PR for that: #5885). I think a way to go would be writing a PRNG Fortuna library.

knoxcard commented at 5:22 AM on September 18, 2016: contributor

Excellent, glad it has been brought to light, it should definitely be removed from the non GUI portion as soon as possible. thank you very much!

luke-jr commented at 4:17 AM on September 22, 2016: member

Wait, so are we broken with OpenSSL 1.1.0?

laanwj commented at 5:39 AM on September 22, 2016: member

I don't know. I'm sure debian Jessie still has 1.0.1 though:

Package: openssl
Version: 1.0.1k-3+deb8u5

The above was the result of a conflict between library linked against and the headers. If both are 1.1.0 it's probably OK, you could try.

leegod commented at 12:18 AM on February 15, 2018: none

I am still met this problem, I can't understand what to do above. Please describe more detailed. I am new at ubuntu.

potadibyo commented at 11:53 AM on August 9, 2018: none

@knoxcard giving me same error

suiguangye commented at 3:35 AM on August 10, 2018: none

I also had the same problem, I think I had the problem because I already had a openssl installed before I try to compile bitcoin, and bitcoin can not find where is the openssl I installed. to be honest I am a new user to ubuntu, So I don't have a simple solution.

My solution is Get a new Ubuntu installed so I will have a clear system, and follow the instruction from https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md which is the bitcoin official instruction for different linux including ubuntu. Then my problem solved.

Maybe remove completely the openssl in your computer first and then follow the instruction will also work, but I don't know.

DrahtBot locked this on Sep 8, 2021