From: "Jörg Krause" <jkrause@posteo.de>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] avahi: fix avahi-ui build with libgtk3
Date: Sun, 02 Nov 2014 21:11:35 +0100 [thread overview]
Message-ID: <1414959095.1061.1.camel@posteo.de> (raw)
In-Reply-To: <20141101191304.GG10189@free.fr>
Yann, Peter, All,
On Sa, 2014-11-01 at 20:13 +0100, Yann E. MORIN wrote:
> J?rg, All,
>
> On 2014-11-01 00:46 +0100, J?rg Krause spake thusly:
> > On Fr, 2014-10-31 at 12:50 +0100, Peter Korsgaard wrote:
> > > commit: http://git.buildroot.net/buildroot/commit/?id=e6c04e6daae674f8983ec2fb106fb897c6803c32
> > > branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
> > >
> > > Fixes:
> > > http://autobuild.buildroot.net/results/daa/daad247db16818f25ab33402e26e27257defbe13/
> > > http://autobuild.buildroot.net/results/720/720e2c8a5eab8b47d2510fe03b4a90ec8beafc17/
> > > http://autobuild.buildroot.net/results/02b/02b4ab9ee07707ee4a4d4ea2b9c67bee91b1392d/
> > > http://autobuild.buildroot.net/results/819/81914317ce82dc1321484d8c2b65647f92aa6929/
> > >
> > > And many others.
> [--SNIP--]
> > This patch breaks building avahi for me. Is autoreconf really intended?
> > Removing it fixed my build.
> >
> > >>> avahi 0.6.31 Autoreconfiguring
> [--SNIP--]
> > configure.ac:419: error: possibly undefined macro:
> > AM_GLIB_GNU_GETTEXT
> > If this token and others are legitimate, please use
> > m4_pattern_allow.
>
> It seems it requires gettext.
>
> J?rg, care to test adding this to avahi.mk (just below AUTORECONF):
>
> AVAHI_GETTEXTIZE = YES
this doesn't help. The problem is the AM_GLIB_GNU_GETTEXT macro at
configure.ac:419. If I enable glibc avahi builds without errors. I've
also found some old posts about this issue, e.g:
http://blogs.gnome.org/jjardon/2010/10/08/use-upstream-gettext-instead-the-glib-one/
I followed this suggestions and replaced AM_GLIB_GNU_GETTEXT with:
AM_GNU_GETTEXT_VERSION([0.19.3])
AM_GNU_GETTEXT([external])
and it works for me.
I am not sure about the version number I should use for gettext. The
most recent one?
I am not an expert about autotools. So what do you think about this? May
I submit a patch for this issue?
Many thanks
J?rg
next prev parent reply other threads:[~2014-11-02 20:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 11:50 [Buildroot] [git commit] avahi: fix avahi-ui build with libgtk3 Peter Korsgaard
2014-10-31 12:40 ` Thomas Petazzoni
2014-10-31 13:19 ` Peter Korsgaard
2014-10-31 13:30 ` Thomas Petazzoni
2014-10-31 16:18 ` Peter Korsgaard
2014-10-31 23:46 ` Jörg Krause
2014-11-01 9:29 ` Peter Korsgaard
2014-11-01 19:13 ` Yann E. MORIN
2014-11-02 20:11 ` Jörg Krause [this message]
2014-11-02 20:16 ` Peter Korsgaard
2014-11-02 21:03 ` Jörg Krause
2014-11-03 9:55 ` Jörg Krause
2014-11-03 20:54 ` Arnout Vandecappelle
2014-11-03 21:04 ` Peter Korsgaard
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=1414959095.1061.1.camel@posteo.de \
--to=jkrause@posteo.de \
--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 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.