|
From: Anders F B. <af...@us...> - 2014-01-07 23:16:47
|
>> Looks like the prebuilt binary is missing a dependency (or maybe it's a distro issue, I can't quite tell): > ... >> error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory > > This has been broken/incompatible between Redhat and Debian, since about forever or so... > > Supposedly one could just provde some compatibility shim that tries to load either soname ? > > > Or force the user to do some creative symlinking... > > Sadly, this seems to be the more popular "answer". The symlink workaround doesn't work, since the library is indeed OpenSSL 1.0.1 only. So it is missing the OPENSSL_1.0.0 symbols anyway, even if the name is symlinked. Guess the only workaround is to actually install libssl.so.1.0.0/libcrypto.so.1.0.0 ? Perhaps this could be added to the feed, with a binary and package-dep on libssl1.0.0 BTW; It doesn't work on RHEL 6 either, this time because it requires glibc > 2.12... I suppose we need some updated RPMS, if this is supposed to build and install easier. --anders |