Quote from: kripz on June 22, 2011, 03:42:37 AM

could be related to my bug where it randomly says cannot authenticate, ill try it when i get home.

It shouldn't help, but I suggest trying it anyway.

Edit: actually, I'm positive that it won't help. What pool are you using? I'd try btcguild.

Quote from: figvam on June 22, 2011, 04:17:50 AM

Quote from: gat3way on June 21, 2011, 07:32:17 PM

Nope, it is impossible to link statically against the SDK as it provides .so only. This is rather strange - and my guess is that sources on sf.net are out of sync with my copy.

I took both the sources and the binary from your site, not from sf.net. But yes, looks like the binary plugin is having trouble communicating with the program compiled from sources.

Quote

OK - we can do the following: I will upload the openssl library from my system - you may download it and copy to /usr/lib, the try again the precompiled version:

http://www.gat3way.eu/poc/libcrypto.so.0.9.8

I'll need libssl.so.0.9.8, too. Thanks.

You don't need 0.9.8, I'm running it just fine with 1.0.0 on Arch Linux.

[gary@snuggles lib]$ ls -lah /usr/lib/ | grep libcrypto
-rw-r--r-- 1 root root 3.5M Feb 8 12:58 libcrypto.a
lrwxrwxrwx 1 root root 18 Feb 8 12:58 libcrypto.so -> libcrypto.so.1.0.0
-r-xr-xr-x 1 root root 2.0M Feb 8 12:58 libcrypto.so.1.0.0

I suggest manually symlinking libcrypto.so and libssl.so to the latest versions (which would be libcrypto.so.1.0.0d and libssl.so..1.0.0d on Fedora, apparently).

sudo ln -s /lib/libcrypto.so /lib/libcrypto.so.1.0.0d
sudo ln -s /lib/libssl.so /lib/libssl.so.1.0.0d

if that doesn't work, rm them and try symlinking against .so.10. Or switch to a distro that doesn't suck Wink