mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: openembedded-core@lists.openembedded.org
Cc: musl@lists.openwall.com, raj.khem@gmail.com
Subject: Re: OpenEmbedded systemd+musl patch status
Date: Fri, 8 Nov 2019 13:51:06 -0500	[thread overview]
Message-ID: <20191108185106.GG16318@brightrain.aerifal.cx> (raw)
In-Reply-To: <20191108184337.GF16318@brightrain.aerifal.cx>

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


      reply	other threads:[~2019-11-08 18:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08 18:43 Rich Felker
2019-11-08 18:51 ` Rich Felker [this message]

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=20191108185106.GG16318@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.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).