From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Removing glibc from the musl .2 ABI
Date: Tue, 16 Jul 2019 23:37:35 -0400 [thread overview]
Message-ID: <20190717033735.GJ1506@brightrain.aerifal.cx> (raw)
In-Reply-To: <b3f33268-7551-fabb-417b-f0fb38f19054@adelielinux.org>
On Thu, Jul 11, 2019 at 06:58:38PM -0500, A. Wilcox wrote:
> (Full disclosure: I am the principal author of gcompat.)
>
> Hi,
>
> Now that gcompat has matured, I was wondering if perhaps musl should
> consider dropping the glibc ABI guarantees when the "2 ABI" lands.
>
> This would make the LFS64 symbol mess completely moot.
This is separate from the .2 ABI topic, but what would you think about
removing glibc ABI-compat from the current .1 ABI and replacing it
with enhanced gcompat? I was thinking ldso could load libgcompat
instead of returning a reference to itself for DT_NEEDED referencing
libc.so.6, and we could move all ABI-compat symbols into gcompat.
The reason I bring it up is that ripping out the LFS64
unwantedly-linkable stuff while keeping it as ABI-only is looking like
more of a pain than I expected.
Rich
next prev parent reply other threads:[~2019-07-17 3:37 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 [this message]
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
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=20190717033735.GJ1506@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).