Bitcoind x86 binary for CentOS
My first obstacle is the missing ecdsa.h (Elliptic Curve Digital Signature Algorithm) file. It’s listed in the man pages for CentOS, but missing from the package, WTF?
Anyway, I guess I can copy it from somewhere else, hopefully I’ll have some binaries for us all soon.
I have successfully built it with 4.8, 4.7 never would but with 4.8 bitcoind locks up whenever it dumps the initial block download to disk. 😐
Just for kicks, tried to compile with DB4.8 got the same error, LOL (the line number was slightly different, but at the same class)
Didn’t get this on other Distros, might be a CentOS related error, but not sure why.
My first obstacle is the missing ecdsa.h (Elliptic Curve Digital Signature Algorithm) file. It’s listed in the man pages for CentOS, but missing from the package, WTF?
Anyway, I guess I can copy it from somewhere else, hopefully I’ll have some binaries for us all soon.
Yes, ecdsa.h is considered patent-encumbered, so Red Hat and other distros turn off ec-dsa.
Yes, Virginia, this means that bitcoin potentially has patent problems.
I have successfully built it with 4.8, 4.7 never would but with 4.8 bitcoind locks up whenever it dumps the initial block download to disk.
I’m probably going to load up a virtual machine of CentOS 5.5 and work with that. I’ve really barfed up the server I was experimenting on trying make it build the binary, LOL.
I have successfully built it with 4.8, 4.7 never would but with 4.8 bitcoind locks up whenever it dumps the initial block download to disk.
I urge you not to use BDB 4.8. The database/log0000* files will be incompatible if anyone uses your build and then goes back to the official build.
Ok, conquered the DB issue after pestering an Oracle developer all day 😛
When you compile DB 4.7.25, you have to use an extra config command or else the compile will be missing those vital header files (why???)
Anyway, here is what it was
../dist/configure --enable-cxx
make
When you compile the source, this fixes the DB compiling related errors.Ah, crap. I totally forgot about that extra flag. I knew about that before from Lazslo’s Linux Build Document. Sorry about that. Get a working build up and running and you’ll definitely be getting some BTC from me. 😄
Oh, but there’s more! 😲
Even after I did that, I couldn’t get it to compile due to linking errors. I was able to get a solid compile of bitcoind though, this is the extra steps it took.
After compiling and installing the BerkeleyDB4.7, you need to add it’s include path to the makefile.unix
Add -I”/usr/local/BerkeleyDB.4.7/include”
Then you need to copy all the libraries from “/usr/local/BerkeleyDB.4.7/lib” to “/usr/lib” BUT WAIT, there’s MORE! 😕
Yes, and if that was not annoying enough, now it will fail to compile because of an OpenSSL error, Grrrrr..
Now you must copy libcrypto.a and libssl.a from “/usr/local/ssl/lib” to “/usr/lib”
Yes, those can be linked, but I got tired of chasing down compiler errors, was easier to just copy them. 🙄
After all of that, then you should be able to compile a bitcoind binary.
I’m testing it now, seems to be working just fine. Downloading blocks and such. When it finishes, I’ll experiment with some coin generation and coin transfer.
I’m still caught on the GUI client compile, currently hangs at
/usr/bin/ld: cannot find -lSM
If anyone is good with Google, let me know. 😉I’ve posted the binary up here (32 bit only - bitcoind): Click Here
There are two versions, one built from stock code, the other modified to accept up to 1,000 nodes (hence the super node name)
Will probably tackle the GUI client build another day, this one wore me out. Donate some BTC to my sig if you are feeling generous 😉
There are two versions, one built from stock code, the other modified to accept up to 1,000 nodes (hence the super node name)
I’d rather you didn’t make a build of the 1000 node connecting version available. It won’t take very many people running that before we have to make another release just to limit the incoming connections.
Quote from: knightmb on August 03, 2010, 11:46:46 PM UTCThere are two versions, one built from stock code, the other modified to accept up to 1,000 nodes (hence the super node name)
I’d rather you didn’t make a build of the 1000 node connecting version available. It won’t take very many people running that before we have to make another release just to limit the incoming connections.
I appreciate your concern; the current release version already limits connections to 8, this one won’t establish hundreds of connections to a single client or node, it’s just modified to allow hundreds of connections back to it from independent clients. I figured since I have the CPU and bandwidth horsepower, why not put it to good use for Bitcoin?
I must have REALLY screwed up my CentOS 5.5 box. This is what I’m getting with my build from the trunk and your build:
Tue Aug 3 15:24:07 CDT 2010
[myles@kappa ~]$ ./bitcoind getinfo
{
"balance" : 0.000000000000000,
"blocks" : 3095,
"connections" : 5,
"proxy" : "",
"generate" : true,
"genproclimit" : -1,
"difficulty" : 1.000000000000000
}
[myles@kappa ~]$ date
Tue Aug 3 15:28:53 CDT 2010
[myles@kappa ~]$ ./bitcoind getinfo
{
"balance" : 0.000000000000000,
"blocks" : 3095,
"connections" : 5,
"proxy" : "",
"generate" : true,
"genproclimit" : -1,
"difficulty" : 1.000000000000000
}Any Ideas?
I’ve been running mine since I made the first post about where to download it.
Everything seems to be fine and the bitcoind is using 100% doing coin generation at the lowest prioirty from when I checked top
knightmb@serverfarm528 32]$ ./bitcoind getinfo
{
"balance" : 0.000000000000000,
"blocks" : 72169,
"connections" : 329,
"proxy" : "",
"generate" : true,
"genproclimit" : -1,
"difficulty" : 244.2132230923753
}From what I can tell on your output, it seems to be hung at that block for some reason. When you stop the daemon and restart it, does it continue on then?
If you want, you can try a direct connect mine with ./bitcoind -server -connect=12.53.130.10 to see if it’s a build thing.