From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14915 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general,gmane.comp.handhelds.openembedded.core Subject: Re: OpenEmbedded systemd+musl patch status Date: Fri, 8 Nov 2019 13:51:06 -0500 Message-ID: <20191108185106.GG16318@brightrain.aerifal.cx> References: <20191108184337.GF16318@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="165902"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mutt/1.5.21 (2010-09-15) Cc: musl@lists.openwall.com, raj.khem@gmail.com To: openembedded-core@lists.openembedded.org Original-X-From: musl-return-14931-gllmg-musl=m.gmane.org@lists.openwall.com Fri Nov 08 19:51:22 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1iT9Lt-000h1b-Kz for gllmg-musl@m.gmane.org; Fri, 08 Nov 2019 19:51:21 +0100 Original-Received: (qmail 17499 invoked by uid 550); 8 Nov 2019 18:51:19 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 17481 invoked from network); 8 Nov 2019 18:51:19 -0000 Content-Disposition: inline In-Reply-To: <20191108184337.GF16318@brightrain.aerifal.cx> Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:14915 gmane.comp.handhelds.openembedded.core:129310 Archived-At: On Fri, Nov 08, 2019 at 01:43:37PM -0500, Rich Felker wrote: > Some questions came up on #musl about systemd and musl > [non-]compatibility, and whether any of the patches being applied are > problematic/buggy, so I'm doing a quick review of my take on each, > from the list here: > > https://git.openembedded.org/openembedded-core/tree/meta/recipes-core/systemd/systemd_243.bb#n31 > https://git.openembedded.org/openembedded-core/tree/meta/recipes-core/systemd/systemd > > > > 0002-don-t-use-glibc-specific-qsort_r.patch > > This looks ok-ish for now. It's not "musl specific" because qsort_r is > not a standard function and historical implementations differ in the > argument order, which is why musl has it -- lack of consensus over ~~~~~~ ?? > something like this is a strong criterion for exclusion. I've been Something got lost in my thought process or typing here. The intended meaning is something like "which is why musl has not yet included it". Rich