From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Preparing to release 0.9.12
Date: Thu, 25 Jul 2013 17:05:23 +0200 [thread overview]
Message-ID: <20130725150522.GJ15323@port70.net> (raw)
In-Reply-To: <20130725104459.3c29fc34@vostro>
* Timo Teras <timo.teras@iki.fi> [2013-07-25 10:44:59 +0300]:
> Relatedly, commit f389c4984a (make the dynamic linker find its path
> file relative to its own location) introduced the armeb, armhf
> variants. Fundamentally, these are distribution specific names. I
> believe debian has/had armeb (big-endian OABI; being retired), arm
> (little-endian OABI; dead port), armel (little-endian EABI), and now
> armhf (little-endian EABI with hard-float). But these are by no means
> standard. While it is good that LDSO_ARCH gets good default with this
> distinguished. It should be allowed to be overridden by distributions.
>
> So basically I'd like to give at configure time:
> DISTRO_ARCH=armel
>
> Which would then make LDSO_ARCH, and SONAME accordingly. And with the
> soname version set, we could do proper binary ugprades (even when not
> everything is yet rebuilt).
why do you care about the name of the loader?
musl could use a random string, the only requirement
is that each abi has a unique identifier so there is
no collision
if the name changes between distros then a simple
binary that only depends on libc becomes non-portable
next prev parent reply other threads:[~2013-07-25 15:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 20:02 Rich Felker
2013-07-25 7:44 ` Timo Teras
2013-07-25 15:05 ` Szabolcs Nagy [this message]
2013-07-25 15:45 ` Timo Teras
2013-07-25 16:39 ` Rich Felker
2013-07-25 16:16 ` Rich Felker
2013-07-25 16:59 ` Timo Teras
2013-07-25 17:18 ` Rich Felker
2013-07-25 17:27 ` Rich Felker
2013-07-26 0:38 ` Isaac
2013-07-26 2:08 ` Rich Felker
2013-07-26 5:13 ` Timo Teras
2013-07-26 5:34 ` Rich Felker
2013-07-26 6:07 ` Timo Teras
2013-07-26 6:18 ` 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=20130725150522.GJ15323@port70.net \
--to=nsz@port70.net \
--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).