A quick thought. Is it as simple as adding openssl build as described above (but with the install step) to the trusty-qt512/Dockerfile?
On Wed, Sep 11, 2019 at 12:18 PM Paul Buxton <paulbuxton.m...@googlemail.com> wrote: > I think that problem is that the bundled ssl library is the wrong one. > We are bundling 1.0, but we need to be bundling 1.1 or newer > > A temporary workaround (for anyone who hits the issue) > cd ~ > git clone https://github.com/openssl/openssl > cd openssl && ./config --prefix=/usr/local/ssl --openssldir=/usr/local/ssl > shared zlib > make > > then run subusrface with > LD_LIBRARY_PATH=$LD_LIBRARY_PATH:~/openssl/ > ./Subsurface-4.9.3-x86_64.AppImage > > Note that I do not perform the install step, so the library is just in the > users home folder. > > I will raise this as an issue and include this info as well. > > Paul > > > On Wed, Sep 11, 2019 at 12:10 PM Dirk Hohndel <d...@hohndel.org> wrote: > >> On Wed, Sep 11, 2019 at 11:56:02AM +0100, Paul Buxton wrote: >> > So the Ubuntu 16 SSL 1.0.0 issue is still there with the Appimage.. >> >> Correct - I couldn't figure out how to make it work without unpacking the >> AppImage and forcing it to use the bundled SSL library. >> >> If you have ideas how to fix the problem, I'm all ears. >> >> /D >> >
_______________________________________________ subsurface mailing list email@example.com http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface