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 21:06:16 +0300 [thread overview]
Message-ID: <20190828180616.GA3044@localhost> (raw)
In-Reply-To: <CAMKF1sroS6zWjdRmh2GLbCF62Hnmifzdr282t8JZBB-ONzd82Q@mail.gmail.com>
What about marking networkmanager as incompatible with musl instead of
maintaining an ever-growing mess?
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.
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 18:06 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 [this message]
2019-08-28 18:53 ` Khem Raj
2019-08-28 19:56 ` Adrian Bunk
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=20190828180616.GA3044@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.