Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Perez de Castro <aperez@igalia.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/avahi: fix build failures
Date: Sun, 3 Dec 2017 13:40:59 +0200	[thread overview]
Message-ID: <20171203134059.GC19380@momiji> (raw)
In-Reply-To: <20171203111344.8661-1-s.martin49@gmail.com>

On Sun,  3 Dec 2017 12:13:44 +0100, Samuel Martin <s.martin49@gmail.com> wrote:
> Since [1], avahi uses/checks for pygobject instead of pygtk, so update
> the configure options accordingly.
> 
> Fixes:
>   http://autobuild.buildroot.net/results/ffea97dc13d379d32f9e33ae6f9e986b2c435ea9
>   and many others
> 
> [1] https://github.com/lathiat/avahi/commit/142124dae6f043085aba59fca4657c56b2b23b65
> 
> Signed-off-by: Samuel Martin <s.martin49@gmail.com>
> ---
>  package/avahi/avahi.mk | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/package/avahi/avahi.mk b/package/avahi/avahi.mk
> index b89887b4c7..c8f1af9a9d 100644
> --- a/package/avahi/avahi.mk
> +++ b/package/avahi/avahi.mk
> @@ -77,7 +77,7 @@ AVAHI_CONF_OPTS = \
>  	--disable-gtk \
>  	--disable-gtk3 \
>  	--disable-gdbm \
> -	--disable-pygtk \
> +	--disable-pygobject \
>  	--disable-mono \
>  	--disable-monodoc \
>  	--disable-stack-protector \
> -- 
> 2.15.1

Reviewed-by: Adrian Perez de Castro <aperez@igalia.com>


--
 Adri?n ?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20171203/4f48a9ab/attachment.asc>

  reply	other threads:[~2017-12-03 11:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-03 11:13 [Buildroot] [PATCH] package/avahi: fix build failures Samuel Martin
2017-12-03 11:40 ` Adrian Perez de Castro [this message]
2017-12-03 22:06 ` 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=20171203134059.GC19380@momiji \
    --to=aperez@igalia.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