From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] libglib2 now requires gettext
Date: Thu, 07 Jul 2011 01:07:12 +0200 [thread overview]
Message-ID: <87d3hnt3dr.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <15734.99.181.179.117.1306510521.squirrel@lavabit.com> (idunham@lavabit.com's message of "Fri, 27 May 2011 08:35:21 -0700 (PDT)")
>>>>> "idunham" == idunham <idunham@lavabit.com> writes:
idunham> I've been trying to build a system with buildroot 2011.05rc2, complete
idunham> with GTK2, which requires libglib2; gettext is enabled for some other
idunham> library.
idunham> So far, buildroot has reached configuring libglib2 for the target system;
idunham> here, it ignores the --disable-nls flag, and goes on to:
idunham> ...
idunham> checking for libintl.h... no
idunham> configure: error:
idunham> *** You must have either have gettext support in your C library, or use the
idunham> *** GNU gettext library. (http://www.gnu.org/software/gettext/gettext.html)
idunham> This with is libglib2-2.28.6
Odd, it works here with this config:
BR2_TOOLCHAIN_BUILDROOT_WCHAR=y
BR2_PACKAGE_LIBGLIB2=y
idunham> So I guess the makefiles need to be changed so as to set gettext as a
idunham> dependency for libglib2, if buildroot uses the latest version.
It already does so (and has done for some time). Could you please
provide some more details about your exact configuration?
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2011-07-06 23:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 15:35 [Buildroot] libglib2 now requires gettext idunham at lavabit.com
2011-05-28 15:16 ` Sérgio Basto
2011-07-06 23:07 ` Peter Korsgaard [this message]
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=87d3hnt3dr.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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