From: "Jörg Krause" <jkrause@posteo.de>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] avahi: fix avahi-ui build with libgtk3
Date: Mon, 03 Nov 2014 10:55:11 +0100 [thread overview]
Message-ID: <1415008511.2065.2.camel@posteo.de> (raw)
In-Reply-To: <20141101191304.GG10189@free.fr>
Yann, Peter,
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
I'd like to discuss some possibilities to solve this issue:
1) forget about patching Makefile.am / running
autoreconf and just strip the CFLAGS arguments in Makefile.in as Peter
suggested
2) replace AM_GLIB_GNU_GETTEXT by AM_GNU_GETTEXT([external]) and update
gettext to a recent version (and maybe intltool too)
3) remove AM_GLIB_GNU_GETTEXT entirely and use only intltool
(additionally update to recent version)
4) add dependency on glib (or glib-gettext, if possible)
My thoughts:
2) I'm not sure why glib version instead of gettext is used here. Maybe
for historical reasons. In autogen this piece of code is used:
# Evil, evil, evil, evil hack
sed 's/read dummy/\#/' `which gettextize` | sh -s -- --copy
--force
which uses GNU gettextize instead of glib-gettextize.
3) I've found some threads about conflicts of using intltool and gettext
together, eg:
https://mail.gnome.org/archives/gtk-devel-list/2012-September/msg00022.html
[Quote] "intltool is a sort-of wrapper around xgetext which interferes
with gettext's own way of setting up po/."
I've tested 2, 3, and 4 and all are building successfully. I've
additionally checked if the .mo files are created in
target/usr/share/locale/.
Best regards
J?rg
next prev parent reply other threads:[~2014-11-03 9:55 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
2014-11-02 20:16 ` Peter Korsgaard
2014-11-02 21:03 ` Jörg Krause
2014-11-03 9:55 ` Jörg Krause [this message]
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=1415008511.2065.2.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.