Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMKF1so4oz8GuoAV+XuvKZ2RY8pw-O-nd1jjiVgxmfjcxQdh2A@mail.gmail.com>
Date: Thu, 11 Jul 2019 17:51:42 -0700
From: Khem Raj <raj.khem@...il.com>
To: musl@...ts.openwall.com
Subject: Re: Removing glibc from the musl .2 ABI

On Thu, Jul 11, 2019 at 4:59 PM A. Wilcox <awilfox@...lielinux.org> 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.
>
> It would also allow musl to "fix" a lot of dumb glibc decisions.  I'm
> thinking specifically here of things like ctermid(3), which musl could
> actually implement correctly if it wasn't being held back by glibc
> defining L_ctermid as 9.
>
> I'm aware this is probably controversial, and it will probably be shot
> down quickly, but I thought I would at least suggest this as an option.
>

I think its too early to drop it but we could provide a configure option
for dropping it and keep the defaults. Since there are enough pre-compiled
apps which probably are not going to change in anytime soon.

> Thank you for your consideration.
>
> Best,
> --arw
>
> --
> A. Wilcox (awilfox)
> Project Lead, Adélie Linux
> https://www.adelielinux.org
>

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.