From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] util-linux compile problems
Date: Mon, 08 Aug 2011 14:13:07 +0200 [thread overview]
Message-ID: <4E3FD2D3.9010107@visionsystems.de> (raw)
In-Reply-To: <1312804690-21977-1-git-send-email-s.neumann@raumfeld.com>
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?
> Now I am getting errors all over the place because
> program_invocation_short_name is not defined. This is correct
> and there's a configure check to test for this. Based on this check
> a fallback is provided by include/c.h. However this file is not
> included from all places that use program_invocation_short_name.
>
> Now I wonder if this would best be fixed by patching all affected
> source files in util-linux or if UCLIBC_HAS_PROGRAM_INVOCATION_NAME
> should be selected when util-linux is selected.
Yegor
next prev parent reply other threads:[~2011-08-08 12:13 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 ` Yegor Yefremov [this message]
2011-08-08 12:24 ` [Buildroot] util-linux compile problems 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
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=4E3FD2D3.9010107@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--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