I had been successfully compiling on x86-64 Linux-Mint and running on x86-64 Debian. However, since moving to nightly and trying to use hyper-tls:
'''let https = HttpsConnector::new()?;'''
it has come to an end with the following error on the target machine:
"error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory"
The target machine says that some libssl and opentls are already installed.
Any solutions please?
It's possible that the build machine and the target machine have different versions of libssl installed. What is the output of dpkg -l libssl* for both machines?
1 Like
Well, yes, for a start one is Ubuntu and the other is Debian:
+++-==============-============-============-=================================
un libssl-dev (no description available)
ii libssl1.0-dev: 1.0.2n-1ubun amd64 Secure Sockets Layer toolkit - de
ii libssl1.0.0:am 1.0.2n-1ubun amd64 Secure Sockets Layer toolkit - sh
ii libssl1.1:amd6 1.1.1-1ubunt amd64 Secure Sockets Layer toolkit - sh
and
ii libssl-dev:amd 1.1.0k-1~deb amd64 Secure Sockets Layer toolkit - de
un libssl-doc (no description available)
un libssl1.0-dev (no description available)
ii libssl1.0.2:am 1.0.2s-1~deb amd64 Secure Sockets Layer toolkit - sh
ii libssl1.1:amd6 1.1.0k-1~deb amd64 Secure Sockets Layer toolkit - sh
Is there a way of getting them synchronised?
No - OpenSSL 1.0.2 and 1.1.0 are not binary compatible. If you want a binary portable between the two, you'll need to statically link to OpenSSL.
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.