mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Kai Peter <kp@lists.qware.org>
To: musl@lists.openwall.com
Subject: [musl] Search path for shared libs
Date: Wed, 20 Apr 2022 09:15:43 +0200	[thread overview]
Message-ID: <db45832f5aaf8257b0233bec08891280@dyndn.es> (raw)

Hi,

I did run in an issue with the search path of shared objects. I'm on a 
real custom system, so the pathes below are correct. There is no glibc 
at all, the gcc was modified to build with the loader in /qlnx/lib. curl 
was build with shared openssl libs as a dependency for git. Then I issue

$ ldd /misc/bin/curl
         /qlnx/lib/ld-musl-x86_64.so.1 (0x7f1e1df97000)
         libcurl.so.4 => /misc/lib/libcurl.so.4 (0x7f1e1df0f000)
         libssl.so.1.1 => /libs/lib/libssl.so.1.1 (0x7f1e1de79000)
         libcrypto.so.1.1 => /libs/lib/libcrypto.so.1.1 (0x7f1e1dbb0000)
         libz.so.1 => /qlnx/lib/libz.so.1 (0x7f1e1db93000)
         libc.so => /qlnx/lib/ld-musl-x86_64.so.1 (0x7f1e1df97000)
         libzstd.so.1 => /qlnx/lib/libzstd.so.1 (0x7f1e1da81000)

All fine, pathes are correct and working. Then:

$ ldd /misc/lib/libcurl.so.4 2>&1 | grep -v reloc
         ldd (0x7f122b691000)
Error loading shared library libssl.so.1.1: No such file or directory 
(needed by /misc/lib/libcurl.so.4)
Error loading shared library libcrypto.so.1.1: No such file or directory 
(needed by /misc/lib/libcurl.so.4)
         libzstd.so.1 => /qlnx/lib/libzstd.so.1 (0x7f122b4f7000)
         libz.so.1 => /qlnx/lib/libz.so.1 (0x7f122b4da000)
         libc.so => ldd (0x7f122b691000)

As a workaround I can create symlinks of the missing ssl libs in 
/qlnx/lib. The ld-musl-x86_64.path contains all pathes and it is read. 
So the question is: Why does libcurl.so.4 not find libssl/libcrypto? Any 
insight?

Kai


             reply	other threads:[~2022-04-20  7:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20  7:15 Kai Peter [this message]
2022-04-20 13:12 ` Rich Felker
2022-04-20 16:03   ` Kai Peter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=db45832f5aaf8257b0233bec08891280@dyndn.es \
    --to=kp@lists.qware.org \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).