From: Justin Cormack <justin@specialbusservice.com>
To: musl@lists.openwall.com
Subject: Re: the case for __MUSL__
Date: Mon, 29 Dec 2014 21:29:22 +0000 [thread overview]
Message-ID: <CAK4o1Ww1-xF_UAGabPtsqFjRGgZsZdKc65n-fPrZ4duCRXp8+Q@mail.gmail.com> (raw)
In-Reply-To: <CAMAJcuB24w8pUKK66YiZUXQNeXxLTXajMvgcGgEYGz2UW1ihZg@mail.gmail.com>
On Mon, Dec 29, 2014 at 5:59 PM, Josiah Worcester <josiahw@gmail.com> wrote:
>
> On Dec 29, 2014 11:51 AM, "Richard Gorton"
> <rcgorton@cognitive-electronics.com> wrote:
>>
>>
>> That is a single example of some of the code in a library which is NOT
>> musl.
>> There are other places in the example library which know about __APPLE__
>> or __GLIBC__ or __sun__
>>
>> My thought is to use __MUSL__ in those libraries as appropriate in place
>> of __<architecture>__ as the backing libc is musl.
>>
>> And said use of __MUSL__ is what I am interested in feedback about.
>>
>
> The intent of not providing it is to force applications to use a portable
> interface rather then being libc specific. So, everyone's leaping to try and
> find ways to not need that.
> Sorry for the mismatched expectations.
There are cases where glibc uses a non standard/bizarre/buggy
interface and using #ifdef __GLIBC__ and leaving Musl to use the sane
default case works. Best to avoid those if at all possible though.
Justin
next prev parent reply other threads:[~2014-12-29 21:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 16:27 Richard Gorton
2014-12-29 17:15 ` Josiah Worcester
2014-12-29 17:17 ` Josiah Worcester
2014-12-29 17:37 ` Rich Felker
2014-12-29 17:51 ` Richard Gorton
2014-12-29 17:59 ` Josiah Worcester
2014-12-29 21:29 ` Justin Cormack [this message]
2014-12-29 21:55 ` 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=CAK4o1Ww1-xF_UAGabPtsqFjRGgZsZdKc65n-fPrZ4duCRXp8+Q@mail.gmail.com \
--to=justin@specialbusservice.com \
--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).