From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] util-linux compile problems
Date: Thu, 11 Aug 2011 09:56:05 +0200 [thread overview]
Message-ID: <1313049366.16546.4.camel@sven> (raw)
In-Reply-To: <87hb5qk6rn.fsf@macbook.be.48ers.dk>
Hi,
On Tue, 2011-08-09 at 16:18 +0200, Peter Korsgaard wrote:
> Sven> Well, it works for me in that configuration as well. But it
> Sven> doesn't work for the configuration that has locale support
> Sven> enabled and gettext/libintl:
>
> Sven> BR2_ENABLE_LOCALE=y
> Sven> BR2_NEEDS_GETTEXT=y
> Sven> BR2_NEEDS_GETTEXT_IF_LOCALE=y
> Sven> BR2_TOOLCHAIN_BUILDROOT_LOCALE=y
> Sven> BR2_PACKAGE_GETTEXT=y
> Sven> BR2_PACKAGE_LIBINTL=y
>
> Sven> I've tried the following patch, but it doesn't seem to help:
>
> Ahh, ok - That's easy to fix, similar to how we do it E.G. with
> avahi. I've committed a fix doing that.
That fix seems to do the trick. But now the build fails when it tries to
install the translations:
Making install in po
make[2]: Entering directory
`/home/sven/git/buildroot/output/build/util-linux-2.19.1/po'
/bin/sh
@MKINSTALLDIRS@ /home/sven/git/buildroot/output/host/usr/arm-unknown-linux-uclibcgnueabi/sysroot/usr/share
/bin/sh: Can't open @MKINSTALLDIRS@
make[2]: *** [install-data-yes] Error 127
Sven
next prev parent reply other threads:[~2011-08-11 7:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 11:58 [Buildroot] util-linux compile problems Sven Neumann
2011-08-08 11:58 ` [Buildroot] [PATCH 1/2] util-linux: fix BR2_PACKAGE_UTIL_LINUX_UUIDD option Sven Neumann
2011-08-08 18:06 ` Peter Korsgaard
2011-08-08 11:58 ` [Buildroot] [PATCH 2/2] util-linux: disable NLS Sven Neumann
2011-08-08 12:13 ` [Buildroot] util-linux compile problems Yegor Yefremov
2011-08-08 12:24 ` Sven Neumann
2011-08-08 18:05 ` Peter Korsgaard
2011-08-08 19:16 ` Peter Korsgaard
2011-08-09 9:50 ` Sven Neumann
2011-08-09 14:18 ` Peter Korsgaard
2011-08-11 7:56 ` Sven Neumann [this message]
2011-08-12 8:28 ` 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=1313049366.16546.4.camel@sven \
--to=s.neumann@raumfeld.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