Russ Allbery wrote:
> I think the situation here is this dependency chain:
>
> libcurl-gnutls -> libldap2 -> libssl
>
> (There may be others; I didn't do a thorough check. Does anyone know if
> there's a tool that will recursively analyze a binary's NEEDED sections
> and build a human-readable graph of the library dependencies?)
I see the following with "libtree -vvv" (output trimmed by hand to just
the paths to libcrypto or libssl):
/usr/lib/git-core/git-remote-https
├── libcurl-gnutls.so.4 [ld.so.conf]
│ ├── libldap.so.2 [ld.so.conf]
│ │ ├── libcrypto.so.3 [ld.so.conf]
│ │ ├── libssl.so.3 [ld.so.conf]
│ │ └── libsasl2.so.2 [ld.so.conf]
│ │ ├── libcrypto.so.3 [ld.so.conf]
│ ├── libssh2.so.1 [ld.so.conf]
│ │ ├── libcrypto.so.3 [ld.so.conf]
--
Robert Edmonds
edmo...@debian.org
