From: Marcus Folkesson <marcus.folkesson@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libostree: make sure libavahi-client is built
Date: Tue, 26 Dec 2017 21:16:09 +0100 [thread overview]
Message-ID: <20171226201609.GA24556@gmail.com> (raw)
In-Reply-To: <CANQCQpZ5v3h_b1_UCK0_08T1pPt5m6Kg-6qmoVRO9LoeOGyjjw@mail.gmail.com>
Matthew,
On Tue, Dec 26, 2017 at 02:06:57PM -0600, Matthew Weber wrote:
> Marcus,
>
> On Mon, Dec 25, 2017 at 10:16 PM, Matthew Weber
> <matthew.weber@rockwellcollins.com> wrote:
> > Marcus,
> >
> > On Thu, Dec 21, 2017 at 5:19 PM, Marcus Folkesson
> > <marcus.folkesson@gmail.com> wrote:
> >> Avahi support also needs libavahi-client, which is built by avahi if avahi-daemon
> >> and dbus is selected.
> >>
> >> Fixes:
> >> http://autobuild.buildroot.net/results/1edfb60add17945eabc557e1dbfb08a0ba466df9/
> >>
> [snip]
>
> >
> > Tested-by: Matt Weber <matthew.weber@rockwellcollins.com>
> >
> > I've kicked off a validation using utils/test-pkg with the following
> > config and both of your libostree patches applied.
> > BR2_TOOLCHAIN_USES_GLIBC=y
> > BR2_PACKAGE_LIBOSTREE=y
> > BR2_PACKAGE_E2FSPROGS=y
> > BR2_PACKAGE_LIBFUSE=y
> > BR2_PACKAGE_LIBGLIB2=y
> > BR2_PACKAGE_LIBGPGME=y
> > BR2_PACKAGE_XZ=y
> > BR2_PACKAGE_AVAHI=y
> > BR2_PACKAGE_AVAHI_DAEMON=y
> > BR2_PACKAGE_DBUS=y
> >
>
> test-pkg looked good with the above config and the case of avahi&dbus disabled.
>
> Matt
Thank you for testing.
Best regards
Marcus Folkesson
next prev parent reply other threads:[~2017-12-26 20:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 23:19 [Buildroot] [PATCH] libostree: make sure libavahi-client is built Marcus Folkesson
2017-12-26 4:16 ` Matthew Weber
2017-12-26 20:06 ` Matthew Weber
2017-12-26 20:16 ` Marcus Folkesson [this message]
2017-12-28 21:56 ` Thomas Petazzoni
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=20171226201609.GA24556@gmail.com \
--to=marcus.folkesson@gmail.com \
--cc=buildroot@busybox.net \
/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