[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130310033952.GD20323@brightrain.aerifal.cx>
Date: Sat, 9 Mar 2013 22:39:52 -0500
From: Rich Felker <dalias@...ifal.cx>
To: musl@...ts.openwall.com
Subject: Re: musl vs. Debian policy
On Sat, Mar 09, 2013 at 10:29:56PM -0500, Rich Felker wrote:
> > Note that /usr/lib/libc.so is a glibc file containing an ld script here.
> >
> > If I remove /usr/lib/ld-musl-x86_64.so.1, the message goes away.
> >
> > But I think it also had something to do with
> > lrwxrwxrwx 1 root root 7 Jan 27 08:29 lib -> usr/lib/
> >
> > I thought the issue was that it found ld-musl-x86_64.so.1 and tried to
> > ensure libc.so points to it, due to the SONAME.
>
> OK, I think we've found something nasty: on your system this warning
> is happening because /usr/lib and /lib are the same directory. On my
> system, /lib/libc.so is being silently created by ldconfig, pointing
> to ld-musl. The latter behavior is much worse; it could cause -lc to
> try to pull in musl, depending on the library path order. I'm working
> on a fix.
Fixed by removing the soname. It was completely unnecessary.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
