chupacabra (OP)
Newbie
Offline
Activity: 3
Merit: 0
|
|
July 12, 2010, 07:27:30 PM |
|
I get this when trying to run bitcoin:
[michael@fed13 64]$ ./bitcoin ./bitcoin: error while loading shared libraries: libcrypto.so.0.9.8: cannot open shared object file: No such file or directory
Fedora 13 uses this:
/lib64/libcrypto.so.1.0.0a
How can I get around this?
I tried a symlink and running ldd and ldconfig to no avail.
Thanks
|
|
|
|
diven
Newbie
Offline
Activity: 14
Merit: 0
|
|
July 12, 2010, 08:05:15 PM |
|
I am having the same issue on Slackware64 13.1.
|
|
|
|
ribuck
Donator
Hero Member
Offline
Activity: 826
Merit: 1060
|
|
July 13, 2010, 03:26:15 PM |
|
I am having the same problem on Fedora 12 32-bit, which also uses libcrypto.so.1.0.0a.
As chupacabra says, a symlink doesn't help because the different library versions contain different symbols.
|
|
|
|
sgtstein
Member
Offline
Activity: 61
Merit: 10
|
|
July 13, 2010, 05:09:31 PM |
|
I too am having issues running it. Same error as above.
Does anyone know how to build it from source on F13? If we could do that, it should work just fine with the new module.
|
|
|
|
|
chupacabra (OP)
Newbie
Offline
Activity: 3
Merit: 0
|
|
July 13, 2010, 06:12:32 PM |
|
I would hope some real developer fixes this so Fedora and Slackware users can use it. No telling what other distros it fails on. What was it built on? I'm guessing Ubuntu/Debian which in my opinion is the most broken fork existing. Please guys. Help us out. Thanks. I'm having my wedding today so I dont have time to code.
|
|
|
|
lachesis
|
|
July 13, 2010, 06:20:24 PM Last edit: July 14, 2010, 12:33:30 AM by lachesis |
|
Mazel tov! Don't be hatin' on Ubuntu though. It's a good OS, and it's helping to drive Linux adoption in the home. Try building yourself when you get some free time on the honeymoon! Alternatively, try this build: (x86_64 only, sorry) http://www.alloscomp.com/bitcoin/bitcoin-r102
|
|
|
|
chupacabra (OP)
Newbie
Offline
Activity: 3
Merit: 0
|
|
July 13, 2010, 06:39:15 PM |
|
|
|
|
|
sgtstein
Member
Offline
Activity: 61
Merit: 10
|
|
July 13, 2010, 07:58:07 PM |
|
Second confirmation that this is the WORKING build for Fedora 13. Thanks!
|
|
|
|
ribuck
Donator
Hero Member
Offline
Activity: 826
Merit: 1060
|
|
July 13, 2010, 09:16:10 PM |
|
Thanks for the link to that binary.
Unfortunately it doesn't work for me. The bash shell gives a "cannot execute binary file" error.
I guess bitcoin-r102 is a 64-bit binary, and I'm running 32-bit Fedora.
|
|
|
|
sgtstein
Member
Offline
Activity: 61
Merit: 10
|
|
July 13, 2010, 10:14:26 PM |
|
Thanks for the link to that binary.
Unfortunately it doesn't work for me. The bash shell gives a "cannot execute binary file" error.
I guess bitcoin-r102 is a 64-bit binary, and I'm running 32-bit Fedora.
True. This is only a 64-bit binary. If no one else gets a binary uploaded tonight, I will try my hand at building one tomorrow morning.
|
|
|
|
ribuck
Donator
Hero Member
Offline
Activity: 826
Merit: 1060
|
|
July 16, 2010, 10:47:17 AM |
|
... I will try my hand at building one ... I'll pledge my first hundred bitcoins to anyone who can post a 32-bit Fedora version. I'd pledge more, except I don't know how many I'll be able to generate. Perhaps other 32-bit Fedora users can add their pledges to mine.
|
|
|
|
|
ribuck
Donator
Hero Member
Offline
Activity: 826
Merit: 1060
|
|
July 16, 2010, 04:45:39 PM Last edit: October 10, 2010, 03:39:05 PM by ribuck |
|
0.3.1 release candidate ... Let me know if that works. Thank you! So far, so good.
|
|
|
|
Odin
Newbie
Offline
Activity: 16
Merit: 0
|
|
July 31, 2010, 01:38:37 AM |
|
I get this when trying to run bitcoin:
[michael@fed13 64]$ ./bitcoin ./bitcoin: error while loading shared libraries: libcrypto.so.0.9.8: cannot open shared object file: No such file or directory
Fedora 13 uses this:
/lib64/libcrypto.so.1.0.0a
How can I get around this?
I tried a symlink and running ldd and ldconfig to no avail.
Thanks
No its a breaking DSO major version change. The problem with Fedora is that it cuts backward compatibility ASAP, where as for RHEL/CentOS there would be compat-openssl providing the libraries you need. # Maybe look at yum search crypto | egrep -i "(ssl|crypto)" # Shot in the dark. yum install compat-openssl I only have Fedora12 (been advised to say away from 13, maybe its unlucky!) Hopefully I can have an OBS build up at https://build.opensuse.org/project/packages?project=home%3Adlmiles over the weekend. This should allow a native Fedora build to exist.
|
|
|
|
jgarzik
Legendary
Offline
Activity: 1596
Merit: 1099
|
|
July 31, 2010, 03:15:05 AM |
|
I get this when trying to run bitcoin:
[michael@fed13 64]$ ./bitcoin ./bitcoin: error while loading shared libraries: libcrypto.so.0.9.8: cannot open shared object file: No such file or directory
Fedora 13 uses this:
/lib64/libcrypto.so.1.0.0a
How can I get around this?
I tried a symlink and running ldd and ldconfig to no avail.
Thanks
No its a breaking DSO major version change. The problem with Fedora is that it cuts backward compatibility ASAP, where as for RHEL/CentOS there would be compat-openssl providing the libraries you need. That is irrelevant to building. bitcoin requires ECDSA, which Fedora will not include due to patent issues. A custom openssl build is a requirement on Fedora, in order to build bitcoin.
|
Jeff Garzik, Bloq CEO, former bitcoin core dev team; opinions are my own. Visit bloq.com / metronome.io Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
|
|
|
Odin
Newbie
Offline
Activity: 16
Merit: 0
|
|
July 31, 2010, 06:11:13 AM |
|
I get this when trying to run bitcoin:
[michael@fed13 64]$ ./bitcoin ./bitcoin: error while loading shared libraries: libcrypto.so.0.9.8: cannot open shared object file: No such file or directory
Fedora 13 uses this: /lib64/libcrypto.so.1.0.0a
How can I get around this?
I tried a symlink and running ldd and ldconfig to no avail. No its a breaking DSO major version change. The problem with Fedora is that it cuts backward compatibility ASAP, where as for RHEL/CentOS there would be compat-openssl providing the libraries you need. That is irrelevant to building. bitcoin requires ECDSA, which Fedora will not include due to patent issues. A custom openssl build is a requirement on Fedora, in order to build bitcoin. This is irrelevant to finding memory leaks. (humour) Yes understood on ECDSA use (and Fedora patent policy), this is a seperate matter and not the question you asked. Your original query was over "running" bitcoin not "building". Hence the reply from me relating to running (and hence my humour comment).
|
|
|
|
|