[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230706162646.GG3630668@port70.net>
Date: Thu, 6 Jul 2023 18:26:46 +0200
From: Szabolcs Nagy <nsz@...t70.net>
To: Alex Xu <alex_y_xu@...oo.ca>
Cc: musl@...ts.openwall.com
Subject: Re: __MUSL__ macro
* Alex Xu <alex_y_xu@...oo.ca> [2023-07-06 08:17:48 -0400]:
> Quoting Alastair Houghton (2023-07-06 06:48:04)
> > Hi all,
> >
> > Before I start, I’m aware of
> >
> > <https://www.openwall.com/lists/musl/2013/03/29/13>
> >
> > but I *still* want to add __MUSL__ (see attached patch).
> >
> > Let me explain what we’re doing, why we want it and why we think musl *should* have it. We’re trying to add support for musl to Swift <https://swift.org <https://swiftlang.org/>> and its attendant core libraries, and there are a number of things about musl that presently differ from other platforms/C libraries we support.
>
> All of these seem to fall at least suspiciously closely to "the usage
> case was badly wrong"...
the problem is not that the usage is wrong, but that
these can change between different versions of musl
(within abi constraints) and header changes can be
backported by distros.
so __MUSL__ cannot solve these issues.
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.
