From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6759 Path: news.gmane.org!not-for-mail From: Josiah Worcester Newsgroups: gmane.linux.lib.musl.general Subject: Re: the case for __MUSL__ Date: Mon, 29 Dec 2014 11:59:39 -0600 Message-ID: References: <20141229173713.GM4574@brightrain.aerifal.cx> <0E7DD0A2-5CD3-4695-AE48-3C95E6FB195B@cognitive-electronics.com> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c26e5c6a5cb2050b5ea393 X-Trace: ger.gmane.org 1419876000 30398 80.91.229.3 (29 Dec 2014 18:00:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 29 Dec 2014 18:00:00 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-6772-gllmg-musl=m.gmane.org@lists.openwall.com Mon Dec 29 18:59:53 2014 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1Y5ebh-00082v-0w for gllmg-musl@m.gmane.org; Mon, 29 Dec 2014 18:59:53 +0100 Original-Received: (qmail 7447 invoked by uid 550); 29 Dec 2014 17:59:51 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 7437 invoked from network); 29 Dec 2014 17:59:51 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Rg+FyYSJcRBuE96efXxFgSF2JHMTn5yLdD1SjLRIf6o=; b=AIY0BBsr/mLaTHwbYuPUVYKLf1pA1bLJxbmsS6sk/RRLB6FK8zShmVdJgKr2KtIuD0 bbQykM9GgZ0r0gI01mx790eKqkpOnR4z4NsnZq2dSGzrJddYyD/yAxXDNmU/vpB6ecHh Zyp+t522UyCUsLDUKVcE97IQemeMpI0QcoLuZK+0SlMa/jOgF02msBm8kfjO9vFHi4Bv +yvDPPsnZwB3bu9TizMlOc9xq2ttSMWL+6yRtqxMUqOgFPF01X9z1uia/b3VLEp5tGd9 kZ9GdGsJ4VgZqlt1V05jfWN1d5M8SaeQJIkF5lHsDvAqf92aIlbNIkW0Uty9aDgn5iP0 45ig== X-Received: by 10.181.29.170 with SMTP id jx10mr84723436wid.50.1419875980039; Mon, 29 Dec 2014 09:59:40 -0800 (PST) In-Reply-To: <0E7DD0A2-5CD3-4695-AE48-3C95E6FB195B@cognitive-electronics.com> Xref: news.gmane.org gmane.linux.lib.musl.general:6759 Archived-At: --001a11c26e5c6a5cb2050b5ea393 Content-Type: text/plain; charset=UTF-8 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 ____ 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. --001a11c26e5c6a5cb2050b5ea393 Content-Type: text/html; charset=UTF-8


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.

--001a11c26e5c6a5cb2050b5ea393--