From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Build failure on msgfmt
Date: Mon, 20 Dec 2010 17:17:48 +0100 [thread overview]
Message-ID: <871v5c1kr7.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20101220150052.662a3707@surf> (Thomas Petazzoni's message of "Mon, 20 Dec 2010 15:00:52 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
Thomas> This is because your gettext package from your distribution is
Thomas> too old, and msgfmt doesn't understand some newer keywords of
Thomas> the libglib2 .po files.
Thomas> Peter, maybe we should build gettext for the host instead of
Thomas> relying on the distribution msgfmt ? What do you think ? Or
Thomas> should be add a check to verify that msgfmt is sufficiently
Thomas> recent ?
Like always, it's a question about pros/cons:
- How many packages need it?
- How uncommon is the dependency? Are there any version dependencies?
- How long does it take to build? Does it have a lot of dependencies?
If gettext comes out positive, then I don't have any issue adding it.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2010-12-20 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 20:52 [Buildroot] Build failure on msgfmt Joe
2010-12-20 14:00 ` Thomas Petazzoni
2010-12-20 16:17 ` 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=871v5c1kr7.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