From: Adrian Bunk <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] libnss-mdns: Stop trying to build for musl
Date: Sun, 19 May 2019 11:37:02 +0300 [thread overview]
Message-ID: <20190519083702.GA23436@localhost> (raw)
In-Reply-To: <c5b0bf78-e579-4f77-c4f2-b16e9ee49eda@gmail.com>
On Sat, May 18, 2019 at 09:56:04PM -0700, Khem Raj wrote:
>
>
> On 5/18/19 10:21 AM, Adrian Bunk wrote:
> > There's no point in building an NSS module for a C library
> > that doesn't support NSS.
> >
>
> Fundamentally this change looks ok however
> have you tried using avahi after this change ?
No.
The RRECOMMENDS in avahi are already _append_libc-glibc,
and libnss-mdns simply cannot work with musl.
How well Avahi works with musl is therefore invariant.
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
prev parent reply other threads:[~2019-05-19 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-18 17:21 [PATCH] libnss-mdns: Stop trying to build for musl Adrian Bunk
2019-05-19 4:56 ` Khem Raj
2019-05-19 8:37 ` 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=20190519083702.GA23436@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