Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC][PATCH] systemd: Remove clearly incorrect musl patches
Date: Sat, 22 Jun 2019 12:39:43 +0300	[thread overview]
Message-ID: <20190622093943.GC9472@localhost> (raw)
In-Reply-To: <CAMKF1soeQ9YreTazqHFbwh-C4AU6H2sr1H5_jNED6+T6K3TTGw@mail.gmail.com>

On Thu, Jun 20, 2019 at 11:09:39AM -0600, Khem Raj wrote:
>...
> musl has provided a lot of good cleanup patches for systemd so this is
> not a wasted
> effort even if upstream systemd does not officially support anything
> besides glibc.
>...

I have yet to see a patch that provides actual benefits for upstream,
and my overall impression of musl support patches is that they do more 
harm than good for everything except making musl build.

Like I have a WTF feeling each time !defined(__GLIBC__) is used instead 
of defined(__MUSL__) for musl-only code - as if there were only two
C libraries in the world.

You already did a lot regarding taking code from gnulib to add glibc
functionality on top of musl, and that's the direction that would
have to be followed for more functionality that is missing in musl
or where musl provides the POSIX version instead of the GNU version
of a function (e.g. strerror_r()).

All this is doable, but it's a lot of hacks and workarounds and
not much in generally useful cleanups.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



      parent reply	other threads:[~2019-06-22  9:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14  7:29 [RFC][PATCH] systemd: Remove clearly incorrect musl patches Adrian Bunk
2019-06-14 11:43 ` Richard Purdie
2019-06-19 19:59   ` Khem Raj
2019-06-20  7:15     ` Adrian Bunk
2019-06-20 17:09       ` Khem Raj
2019-06-20 17:38         ` Martin Jansa
2019-06-22  9:39         ` Adrian Bunk [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=20190622093943.GC9472@localhost \
    --to=bunk@stusta.de \
    --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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox