From: Adrian Bunk <bunk@stusta.de>
To: "Andreas Müller" <schnitzeltony@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: musl thoughts
Date: Sat, 23 Mar 2019 23:53:36 +0200 [thread overview]
Message-ID: <20190323215336.GA22469@localhost> (raw)
In-Reply-To: <CALbNGRQPtnNLSVhDzXgnvn-2VNPPMfQTY5vDdwM3xr5iVcGofg@mail.gmail.com>
On Sat, Mar 23, 2019 at 10:22:15PM +0100, Andreas Müller wrote:
> On Sat, Mar 23, 2019 at 10:16 PM Adrian Bunk <bunk@stusta.de> wrote:
> >
> > On Fri, Mar 22, 2019 at 03:18:01PM -0700, Khem Raj wrote:
> > >...
> > > There are certain design aspects of musl which are actually turning
> > > out to be good
> > > e.g. there is no __MUSL__ define, so non-portable code can not be
> > > hidden which is a good thing,
> > >...
> >
> > Please take a closer look at some of the musl changes to NM that made
> > upgrading NM so hard for Andreas.
> >
> > +#if defined(__GLIBC__)
> > #include <net/ethernet.h>
> > +#else /* musl libc */
> > +#define ETH_ALEN 6 /* Octets in one ethernet addr */
> > +#endif
> >
> > Using __GLIBC__ in workarounds for bugs in musl is wrong,
> > and cannot be upstreamed since it would do the wrong thing
> > on other non-broken C libraries.
> >
> > > While the eyes may hurt
> > > to see them, it does serve a
> > > good reminder of whats needed for a given package.
> > >...
> >
> > Who is responsible for fixing the root causes of such bugs in musl,
> > so that the workaround patches can be dropped from packages like NM?
> >
> > cu
> > Adrian
> If I am not mistaken nobody is responsible. It is recipe wise: Sending
> out a patch that fails for musl is rejected usually.
As you have experienced, it does create a huge technical debt to ship
workaround patches in several recipes instead of fixing the bug in musl.
> The last example could be fixed easily at musl shipping a ethernet.h containing
> #define ETH_ALEN 6
>...
That's already shipped by musl.
But there seems to be some incompatibility between musl and the
kernel headers used by musl.
This has to be sorted out in musl and/or the kernel headers.
> Andreas
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
next prev parent reply other threads:[~2019-03-23 21:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 1:11 musl thoughts Andreas Müller
2019-03-22 14:53 ` akuster808
2019-03-22 19:35 ` Adrian Bunk
2019-03-22 20:03 ` Adrian Bunk
2019-03-22 22:20 ` Khem Raj
2019-03-23 17:30 ` Adrian Bunk
2019-03-22 22:18 ` Khem Raj
2019-03-23 21:16 ` Adrian Bunk
2019-03-23 21:22 ` Andreas Müller
2019-03-23 21:53 ` Adrian Bunk [this message]
2019-03-23 22:00 ` Andreas Müller
2019-03-25 15:36 ` Andrea Adami
2019-03-25 16:10 ` Adrian Bunk
2019-03-25 16:26 ` Andreas Müller
2019-03-25 17:15 ` Andreas Müller
2019-03-25 17:36 ` Andreas Müller
2019-03-25 18:03 ` Adrian Bunk
2019-03-25 19:46 ` Andreas Müller
2019-03-25 17:46 ` Adrian Bunk
2019-03-25 21:11 ` Andreas Müller
2019-03-25 22:38 ` Khem Raj
2019-03-25 16:31 ` Andrea Adami
2019-03-25 17:07 ` Adrian Bunk
2019-03-25 17:44 ` Khem Raj
2019-03-25 18:23 ` Adrian Bunk
2019-03-25 15:46 ` Mark Hatle
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=20190323215336.GA22469@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=schnitzeltony@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