musl - Ignoring dependencies libresolv and libcrypt

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <c69ba3b1-9ac2-9cf3-002e-764265dd69a1@arrikto.com>
Date: Wed, 2 Sep 2020 19:14:10 +0300
From: Nikos Dragazis <ndragazis@...ikto.com>
To: musl@...ts.openwall.com
Subject: Ignoring dependencies libresolv and libcrypt

Hi everyone,

Apologies if this has already been answered before.

I am experimenting with musl. I see that musl produces a single DSO with
all symbols, as opposed to glibc which produces multiple DSOs
(libthread, libm, librt, etc.). I also notice that musl generates some
empty archives for compatibility reasons, namely the
lib{crypt,dl,m,pthread,resolv,rt,util,xnet}.a. These are already
documented in the FAQ [1].

By looking at the code [2], I see that musl's dynamic linker ignores
dynamic dependencies with names lib{c,pthread,rt,m,dl,util,xnet} and
this makes sense based on the above.

What doesn't make sense to me is that musl's dynamic linker does not
ignore dynamic dependencies with names libresolv and libcrypt. Is there
a reason for this?

Thanks in advance,
Nikos

[1] https://wiki.musl-libc.org/faq.html#Q:-lib(m|pthread|crypt).a/so-are-empty?
[2] https://git.musl-libc.org/cgit/musl/tree/ldso/dynlink.c#n991

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.