Also note that it works if I put the compiled libssl path at the end of the LD_LIBRARY_PATH like so LD_LIBRARY_PATH=/tmp/.mount_SubsurCt4MZJ/usr/lib/:$LD_LIBRARY_PATH:~/local/openssl/ /tmp/.mount_SubsurCt4MZJ/AppRun -v
On Mon, Sep 9, 2019 at 1:18 PM Paul Buxton <[email protected]> wrote: > Yes it will use the same path, but if QT is looking for different versions > it may find both the one in the package and the one on the platform. > Is that the first or last reference to libssl you get in strace? > > I have now downloaded and built openssl locally. > If I add its folder to LD_LIBRARY_PATH before running then it all looks to > work. > > Attached the strace .... | grep ssl of both with and without this added to > the path. > > I do see the same reference to libssl in my strace, but further down in > the strace log there are some more calls to open libssl, and afterwards a > failure to resolve OPENSLL_init_ssl > > Doing nm -aD on the library in the appimage confirms that this symbol is > not present, but it is present in the version of libssl I have built > locally. > > > > > On Mon, Sep 9, 2019 at 12:21 PM Dirk Hohndel <[email protected]> wrote: > >> On Mon, Sep 09, 2019 at 11:26:22AM +0100, Paul Buxton wrote: >> > Hmm, doesn't make any difference on mine. >> > Googling I did fine some references that suggest that Qt networking >> loads >> > libssl and libcrypto using dlopen, which would not show up as a >> dependency >> > through ldd.... >> > >> https://code.qt.io/cgit/qt/qtbase.git/tree/src/network/ssl/qsslsocket_openssl_symbols.cpp >> > So whilst ldd is listing that it is linked against 1.0 it may actually >> be >> > picking up 1.1 from your library path. >> >> But dlopen() should use the same LD_LIBRARY_PATH, right? >> >> Anyway, I ran this through strace and I am indeed opening the 1.0 library: >> >> openat(AT_FDCWD, >> "/tmp/.mount_SubsurzTksC9/usr/bin/../lib/libssl.so.1.0.0", >> O_RDONLY|O_CLOEXEC) = 3 >> >> Could you check which one you are opening? >> >> /D >> >>
_______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
