Re: [Zero-install-devel] 0install 2.6-rc2

[Thomas L. <ta...@gm...>]

On 7 January 2014 23:16, Anders F Björklund <af...@us...> wrote:
>>> 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...
>> Basically Fedora just makes something up at random:

Wow. That's crazy. Thanks for the explanation!

>> 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.

I've built new binaries (2.6-rc3) against upstream openssl and
libcurl, so hopefully untainted by Debian or Fedora craziness. Anyway,
the symbol versions seem to be gone :-)

> 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.


-- 
Dr Thomas Leonard        http://0install.net/
GPG: 9242 9807 C985 3C07 44A6  8B9A AE07 8280 59A5 3CC1
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA