From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Progress on roadmap to 0.9.13
Date: Fri, 16 Aug 2013 02:25:36 -0400 [thread overview]
Message-ID: <20130816062536.GX221@brightrain.aerifal.cx> (raw)
In-Reply-To: <1376634070.2737.41@driftwood>
On Fri, Aug 16, 2013 at 01:21:10AM -0500, Rob Landley wrote:
> On 08/15/2013 02:59:12 AM, Rich Felker wrote:
> >One key target for 0.9.13 which I didn't cover above is improving
> >"make install" and possibly tweaking the symlink strategy for libc.so
> >and ld-musl.so. At several times in the past, I was fairly convinced
> >that it makes more sense to reverse the symlink direction and have
> >libc.so point to ld-musl.so rather than the other way around. However,
> >I keep going back to doubting that there's any good reason for it to
> >change. So if there are people who still care about this issue, I'd
> >really like to hear you speak up _now_ rather than 2 days before the
> >next release, or after the next release.
>
> Which makes it easier to install uClibc and musl and bionic next to
> each other? (You can have /lib/musl and /lib/uClibc and /lib/bionic
> for most of the .so and .a files, but the dynamic linker is a
> hardwired abspath in each binary and then the linker would be what
> searches the more specific path...)
Makes no difference. Either way, the dynamic linker is intended to be
in /lib and everything else can be wherever you want it to be.
Rich
next prev parent reply other threads:[~2013-08-16 6:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 7:59 Rich Felker
2013-08-16 6:21 ` Rob Landley
2013-08-16 6:25 ` Rich Felker [this message]
2013-08-17 9:39 ` Timo Teras
2013-08-17 12:39 ` Matias A. Fonzo
2013-08-17 15:39 ` orc
2013-08-17 16:33 ` Rich Felker
2013-08-17 16:49 ` Christian Neukirchen
2013-08-17 16:29 ` Rich Felker
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=20130816062536.GX221@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--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).