From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] util-linux compile problems
Date: Mon, 08 Aug 2011 14:24:13 +0200 [thread overview]
Message-ID: <1312806444.22342.4.camel@sven> (raw)
In-Reply-To: <4E3FD2D3.9010107@visionsystems.de>
On Mon, 2011-08-08 at 14:13 +0200, Yegor Yefremov wrote:
> Hi Sven,
>
> > after updating buildroot we are getting compile errors from building
> > util-linux. First the linker was complaining that it couldn't find
> > libintl_gettext and related symbols. I was able to fix that by
> > passing --disable-nls to the configure script (patch follows).
>
> I've tried the 2.20-rc1 and also found this problem, that I didn't see
> before. I got rid of it by selecting libintl and adding it to build
> dependencies. Could you try this?
Well, I don't think that libintl should be selected only because a few
tools from util-linux gain native language support then. But I agree
that it might be better only to use --disable-nls if libintl is not
selected already.
Sven
next prev parent reply other threads:[~2011-08-08 12:24 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 [this message]
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
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=1312806444.22342.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