From: Christian Neukirchen <chneukirchen@gmail.com>
To: musl@lists.openwall.com
Subject: Re: musl vs. Debian policy
Date: Fri, 08 Mar 2013 16:13:59 +0100 [thread overview]
Message-ID: <8762117wlk.fsf@gmail.com> (raw)
In-Reply-To: <20130308004118.GX20323@brightrain.aerifal.cx> (Rich Felker's message of "Thu, 7 Mar 2013 19:41:19 -0500")
Rich Felker <dalias@aerifal.cx> writes:
> On Thu, Mar 07, 2013 at 07:17:56PM +0100, Christian Neukirchen wrote:
>> Rich Felker <dalias@aerifal.cx> writes:
>>
>> > On Wed, Mar 06, 2013 at 03:29:13PM -0800, Isaac Dunham wrote:
>> >> The apparent solution to this is to ship only the dynamic linker,
>> >> since this is all we need (the dependency on libc.so is disregarded
>> >> when it comes to running dynamically linked programs). But
>> >> currently, actually doing this would be somewhat of a hack.
>> >>
>> >> Is there any prospect of installing lib/libc.so straight to
>> >> ${LDSO_PATHNAME} ? I'm thinking it could be done via something like:
>> >
>> > This has been proposed before, and the main obstacle was build-system
>> > difficulties if I remember right. I'd still like to consider doing it,
>> > but it would be nice to be able to do it for its own sake rather than
>> > for the sake of satisfying distro policy being applied where it
>> > doesn't make sense. Maybe we can try to figure out Debian's stance
>> > before we rush into making the change for their sake.
>>
>> In this case, could we also change the SONAME of the library itself to
>> something not libc.so? It would avoid this "bogus" warning of glibc
>> ldconfig...
>
> No, this is a lot more problematic and I see no benefits. For each
> possible SONAME musl may have been linked by, musl must contain a
> special-case to refuse to load this SONAME when it appears in
> DT_NEEDED. "libc.so" is a name that should never appear elsewhere. I
> don't want to keep expanding this list of names, and of course
> programs linked using a new SONAME would be gratuitously incompatible
> with an older musl ld.so that didn't have the new name included in its
> refuse-to-load list.
ld-musl-x86_64.so shouldn't appear elsewhere either.
>> ldconfig: /usr/lib/libc.so is not a symbolic link
>
> IIRC this is happening due to some other misconfiguration. If nothing
> else, it means glibc and musl were both installed in /usr/lib, or
> ldconfig is configured for the wrong paths (since ldconfig has nothing
> to do with musl).
This happens because /lib/ld-musl-x86_64.so.1 has a SONAME of libc.so
(which should be the correct place). The message is not harmful, but
annoying.
--
Christian Neukirchen <chneukirchen@gmail.com> http://chneukirchen.org
next prev parent reply other threads:[~2013-03-08 15:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 23:29 Isaac Dunham
2013-03-07 13:04 ` Rich Felker
2013-03-07 18:17 ` Christian Neukirchen
2013-03-07 18:45 ` Kurt H Maier
2013-03-07 18:49 ` Daniel Cegiełka
2013-03-08 0:41 ` Rich Felker
2013-03-08 15:13 ` Christian Neukirchen [this message]
2013-03-09 1:27 ` Rich Felker
2013-03-09 20:08 ` Christian Neukirchen
2013-03-10 3:29 ` Rich Felker
2013-03-10 3:39 ` Rich Felker
2013-03-08 1:03 ` Isaac Dunham
2013-03-08 1:10 ` Rich Felker
2013-03-08 4:03 ` Isaac Dunham
2013-03-09 1:23 ` Rich Felker
2013-03-07 18:56 ` Justin Cormack
2013-03-08 0:04 ` Isaac Dunham
2013-03-07 22:30 ` Rob Landley
2013-03-08 0:22 ` Isaac Dunham
2013-03-08 1:09 ` Kurt H Maier
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=8762117wlk.fsf@gmail.com \
--to=chneukirchen@gmail.com \
--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).