Skip to main content

Building bitcoin/litecoin on mac os x missing EC.h

For my own fun, I was playing around with bitcoin, to check how the parameters of the cryptocurrencies can be modified.

 After recent upgrades to my OS, I could not build any longer the bitcoind. Seems like something changed on that side. Now this command
./configure --with-gui=qt5 --enable-debug

Was sistematically producing 

configure: error: OpenSSL ec header missing


EC is the file for elliptic curve cryptography. I had brew correctly configured, and the header files were all correctly present. After some time spent inspecting the issue, on github I was able to find the solution for this problem. I simply add to export the following



export LDFLAGS=-L/usr/local/opt/openssl/lib









export CPPFLAGS=-I/usr/local/opt/openssl/include







There is aksi pull request on bitcoin for that, I hope I could save you some time





https://github.com/bitcoin/bitcoin/pull/6885/files?diff=split&unchanged=expanded

Comments

Unknown said…
I have the same problem. Through

brew info openssl,

it says something like
"openssl ... (bottled).

Does that mean the openssl from brew doesn't have certain cipher like ec?

I tried to compile from source code myself, but haven't been able to solve the problem. It can be that I messed up at some steps. It will be very helpful if there is automatic step like brew for OsX.
11/15/2015 04:17:00 AM
Francesco De Collibus said…
When something is bottled into brew, it means is not automatically linked in /usr/local/lib . This happens because mac os x is shipped with another openssl implementation who could potentially conflict with the one from brew. That's why it's not automatically linked, but you have to explicitly do it
11/15/2015 06:28:00 PM
Post a Comment

Popular posts from this blog

Multiple controllers with Spring Boot

Remember, when you want to have multiple controllers with Spring Boot, you should always name them differently in the annotation, otherwise they will not work So these two together will NOT work (or just one of them will work) These two instead WILL work.
2 comments
Read more

Can't use the newest npm when node is installed with brew (MacOs)

Even though I installed and reinstalled node with brew, with last versione 11.8.0, apparently it kept using the last version fdecollibus$ npm install --global gatsby-cli npm WARN npm npm does not support Node.js v11.8.0 npm WARN npm You should probably upgrade to a newer version of node as we npm WARN npm can't make any promises that npm will work with this version. npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9. npm WARN npm You can find the latest version at https://nodejs.org/ /usr/local/Cellar/node/11.8.0/bin/gatsby -> /usr/local/Cellar/node/11.8.0/lib/node_modules/gatsby-cli/lib/index.js + gatsby-cli@2.4.8 npm -v gave me back version 5.6.0. I've therefore noticed that  /usr/local/lib/node_modules had wrong permissions assigned to root:wheel. A chown did not fix the problem: I've had to manually delete the content of the folder (cd / usr/local/lib/node_modules and -careful - type rm -rf ...
Post a Comment
Read more