From: orc <orc@sibserver.ru>
To: musl@lists.openwall.com
Subject: Re: Progress on roadmap to 0.9.13
Date: Sat, 17 Aug 2013 23:39:43 +0800 [thread overview]
Message-ID: <20130817233943.6c591ddf@sibserver.ru> (raw)
In-Reply-To: <20130817123913.771df1d0@vostro>
On Sat, 17 Aug 2013 12:39:13 +0300
Timo Teras <timo.teras@iki.fi> wrote:
> On Thu, 15 Aug 2013 03:59:12 -0400
> Rich Felker <dalias@aerifal.cx> 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. If
> > there's no progress on justifying changes, I think the only changes
> > I'm going to make in this area are to fix lack-of-atomicity issues
> > during installation.
>
> Sorry for late answer.
>
> IIRC the advantages were:
>
> - Easier to install different subarch (even compatible arch versions)
> side by side. As ld.so names are unique - libc.so is same for all so
> those would need to be renamed anyway.
>
> - libc.so and libc.a can go to /usr/lib if libc.so is just an
> optional symlink. this is desirable as the development stuff are not
> nice to keep in /lib.
>
> So I would at least like to have the symlink direction changed.
>
> Or alternatively have something like:
> /lib/libc-arch.so.<abiver>
> /lib/ld-musl-<arch>.so.1 -> libc-arch.so.<abiver
> /usr/lib/libc.so -> /lib/libc.so.<abiver>
> /usr/lib/libc.a
>
> Allowing of course /usr/lib to be a toolchain specific prefix.
>
> - Timo
I generally don't like the idea of symlink change, but if it will go, I
will not argue. But, how existing installs will resolve that change
in one pass during install? Do I need static busybox to manually
replace symlink?
I even suggest making a hard link between them, so no symlink issue
will be there :)
It requires a bit more work without benefit. Point me please to
benefits page/mail, because I lost in my imap cache.
next prev parent reply other threads:[~2013-08-17 15:39 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
2013-08-17 9:39 ` Timo Teras
2013-08-17 12:39 ` Matias A. Fonzo
2013-08-17 15:39 ` orc [this message]
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=20130817233943.6c591ddf@sibserver.ru \
--to=orc@sibserver.ru \
--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).