From: Adrian Bunk <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-networking][RFC PATCH 0/1] Failed to compile networkmanager with musl
Date: Wed, 28 Aug 2019 22:56:35 +0300 [thread overview]
Message-ID: <20190828195635.GB3044@localhost> (raw)
In-Reply-To: <CAMKF1sq84RHmHY3dyj7rpO=w3xDQry3jAHG6ZeOiQvLMiMnRVg@mail.gmail.com>
On Wed, Aug 28, 2019 at 11:53:27AM -0700, Khem Raj wrote:
> On Wed, Aug 28, 2019 at 11:06 AM Adrian Bunk <bunk@stusta.de> wrote:
> >
> > What about marking networkmanager as incompatible with musl instead of
> > maintaining an ever-growing mess?
> >
>
> if the fix is specifically done for musl alone then I would agree, but
> in many cases, the fixes
> have been cleaning up assumptions in kernel UAPI headers on glibc
> provided headers
> which is a good thing, and it does take some time for kernel header
> changes to flow upstream
> but eventually, they do. e.g. see [1]
This is not a cleanup, this is a workaround for a misfeature of musl.
The kernel userspace headers are the userspace ABI of the kernel for
usage by all C libraries provided in one place, they are not tied to
any specific C library.
musl upstream does not even try to use the kernel userspace headers.
The kernel userspace headers used to be a mess, but after more than 10
years of cleanup there is no excuse for musl to insist on providing own
definitions of what is already provided by the kernel headers.
> > Networkmanager uses parts of systemd as a library and also has own
> > glibc-only usages.
> >
> > Both systemd and networkmanager are fundamentally Linux-only,
> > and for systemd it is known that upstream has made the design
> > decision to not compromise their software for rare usecases
> > with C libraries other than glibc.
> >
> > AFAIK OE is the only distribution trying to build either of these
> > with musl, other musl-using distributions are using less heavyweight
> > solutions.
>
> We should enable as much as possible we can and not go overboard in
> supporting everything
> except for core packages where it might be ok to put a bit of effort
> and upstream the changes
> network manager is quite useful in base images eg. xfce images etc
>...
When you are using networkmanager and xfce in your image,
what is the point of using musl instead of glibc?
Networkmanager alone has twice the size of glibc.
There is a benefit of a small C library when your flash space is
single-digit megabytes, but maintaining plenty of not upstreamable
OE-only patches for using networkmanager on musl without a sane
usecase is a waste of effort.
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-08-28 19:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 3:43 [meta-networking][RFC PATCH 0/1] Failed to compile networkmanager with musl kai.kang
2019-08-28 3:43 ` [RFC PATCH 1/1] networkmanager: 1.18.2 -> 1.20.0 kai.kang
2019-08-28 4:27 ` [meta-networking][RFC PATCH 0/1] Failed to compile networkmanager with musl Khem Raj
2019-08-28 12:33 ` Bruce Ashfield
2019-08-29 1:39 ` Kang Kai
2019-08-28 18:06 ` Adrian Bunk
2019-08-28 18:53 ` Khem Raj
2019-08-28 19:56 ` Adrian Bunk [this message]
2019-08-28 20:32 ` Khem Raj
2019-08-28 21:40 ` Adrian Bunk
2019-08-29 1:47 ` Kang Kai
2019-08-29 1:57 ` Khem Raj
2019-08-29 2:01 ` Kang Kai
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=20190828195635.GB3044@localhost \
--to=bunk@stusta.de \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.