From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 1/1] package/avahi: configure option pygtk was renamed to pygobject
Date: Tue, 28 Nov 2017 14:37:12 +0100 [thread overview]
Message-ID: <20171128133712.GH2889@scaer> (raw)
In-Reply-To: <20171128131715.cfuxo2ehjtpkvswy@tarshish>
Baruch, All,
On 2017-11-28 15:17 +0200, Baruch Siach spake thusly:
> On Tue, Nov 28, 2017 at 02:06:15PM +0100, Yann E. MORIN wrote:
> > On 2017-11-27 21:27 +0100, Bernd Kuhls spake thusly:
> > > See corresponding commit:
> > > https://github.com/lathiat/avahi/commit/142124dae6f043085aba59fca4657c56b2b23b65
> > >
> > > Fixes
> > > http://autobuild.buildroot.net/results/1e9/1e974c814ae4236077a869339be1143a9af7e5cd/
> > > http://autobuild.buildroot.net/results/010/0101b1205aec5a0c9c6509edf3d302aeaa3bd0ca/
> > > http://autobuild.buildroot.net/results/572/5721634ffa2a4544a82dda08c1fcea331ecdadaf/
> > >
> > > Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> > > ---
> > > 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 \
> >
> > This is incorrect, because then this disables the full python support.
> >
> > So, either we do without python-gobject and we remove all the python
> > handling in avahi.mk, or we bump python-gobject and fix the dependency
> > chain.
>
> Newer versions of python-gobject depend on GObject introspection. Buildroot
> does not currently support introspection.
>
> http://lists.busybox.net/pipermail/buildroot/2017-February/184645.html
So, we'll have to do without python support in avahi... :-/
However, coming back to the original problem. Disabliong pygobject does
disable building of avahi-python:
Building avahi-python: no (You need python, pygobject and python-dbus!)
But it seems that python support might still be enabled:
Enable Python: yes
But none of the ELF files installed by avahi depend on libpython.
That's weird...
Bernd, the commit log should explain all this...
> Cross compiling introspection is a painful exercise:
> http://patchwork.ozlabs.org/patch/828791/
Yep, I'm aware of that effort. This gobject introspection is a real PITA...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-11-28 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 20:27 [Buildroot] [PATCH/next 1/1] package/avahi: configure option pygtk was renamed to pygobject Bernd Kuhls
2017-11-28 13:06 ` Yann E. MORIN
2017-11-28 13:17 ` Baruch Siach
2017-11-28 13:37 ` Yann E. MORIN [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=20171128133712.GH2889@scaer \
--to=yann.morin.1998@free.fr \
--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