From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Removing glibc from the musl .2 ABI
Date: Wed, 24 Jul 2019 17:31:29 -0400 [thread overview]
Message-ID: <20190724213129.GG1506@brightrain.aerifal.cx> (raw)
In-Reply-To: <20190724173600.GT21055@port70.net>
On Wed, Jul 24, 2019 at 07:36:00PM +0200, Szabolcs Nagy wrote:
> * James Y Knight <jyknight@google.com> [2019-07-24 09:33:05 -0700]:
> > One thing I've not seen mentioned yet: if this is done, then anyone
> > (whether intentionally or inadvertently) who links any glibc-compiled .o or
> > .a files into a musl binary/shared-lib will be broken.
> >
> > Up until now, with musl's mostly-glibc-compatible ABI, you could link the
> > two object files together, and generally expect it to work. When
> > compatibility is instead done with magic in the dynamic loader, that
> > obviously can only ever work with a shared-object boundary.
> >
> > I don't know if anyone actually uses musl in a context where this is likely
> > to be a problem, but it at least seems worth discussing (and loudly
> > documenting as a warning to users not to do this if implemented).
>
> is it common that binary only .o or .a is distributed?
>
> binary only shared libs with glibc dependency are fairly
> common (plugins, userspace driver code etc). i think the
> abi compat was mainly intended to support that.
It may be common with proprietary middleware or userspace-drive stuff
for hardware devices, where presumably the idea of shipping a static
lib rather than a shared one is that you don't ship usable copies of
the middleware vendor's library too your customers along with your
product.
Rich
next prev parent reply other threads:[~2019-07-24 21:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 23:58 A. Wilcox
2019-07-12 0:51 ` Khem Raj
2019-07-12 1:45 ` Rich Felker
2019-07-12 1:47 ` Rich Felker
2019-07-17 3:37 ` Rich Felker
2019-07-17 13:13 ` A. Wilcox
2019-07-17 15:11 ` Rich Felker
2019-07-17 18:10 ` A. Wilcox
2019-07-17 18:16 ` Rich Felker
2019-07-22 15:52 ` Rich Felker
2019-07-24 15:17 ` Szabolcs Nagy
2019-07-24 16:02 ` Rich Felker
2019-07-24 16:33 ` James Y Knight
2019-07-24 17:36 ` Szabolcs Nagy
2019-07-24 21:31 ` Rich Felker [this message]
2019-07-24 21:29 ` Rich Felker
2019-07-25 16:42 ` James Y Knight
2019-07-25 20:03 ` 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=20190724213129.GG1506@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).