From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] avahi: fix avahi-ui build with libgtk3
Date: Sun, 02 Nov 2014 21:16:19 +0100 [thread overview]
Message-ID: <87ppd55pf0.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1414959095.1061.1.camel@posteo.de> ("Jörg Krause"'s message of "Sun, 02 Nov 2014 21:11:35 +0100")
>>>>> "J?rg" == J?rg Krause <jkrause@posteo.de> writes:
Hi,
> Yann, Peter, All,
>> 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.
glib, not glibc.
> 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?
Sorry, don't know.
> I am not an expert about autotools. So what do you think about this? May
> I submit a patch for this issue?
Either that, or we simply forget about patching Makefile.am / running
autoreconf and just strip the CFLAGS arguments in Makefile.in instead.
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2014-11-02 20:16 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 [this message]
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=87ppd55pf0.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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