From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: help2man-native: task configure fails with `configure: error: perl module Locale::gettext required`
Date: Thu, 10 Mar 2011 10:40:20 -0700 [thread overview]
Message-ID: <4D790D04.5050409@mentor.com> (raw)
In-Reply-To: <201103101722.55323.pgsellmann@portner-elektronik.at>
On 03/10/2011 09:22 AM, Peter Gsellmann wrote:
> Am Donnerstag, 10. März 2011, 16:40:36 schrieb Marco Cavallini:
>> Tom Rini ha scritto, Il 10/03/2011 16:04:
>>
>>>
>>> Is this a uclibc target perhaps?
>>>
>>
>> Hi Tom,
>>
>> Not mine, is this
>>
>> Build Configuration:
>> BB_VERSION = "1.10.2"
>> METADATA_BRANCH = "master"
>> METADATA_REVISION = "40a8506"
>> TARGET_ARCH = "arm"
>> TARGET_OS = "linux-gnueabi"
>> MACHINE = "ronetix-pm9263"
>> DISTRO = "angstrom"
>> DISTRO_VERSION = "2010.7-test-20110310"
>> TARGET_FPU = "soft"
>>
>
> here also glibc-2.9
>
> Found this: reverting patch bccf626b1428d7087d261bf4ad91744b5b5d5418 helped.
>
> 'inherit gettext' is not a full replacement for DEPENDS = "gettext-native"
>
> Same problem and solution for packages e2fsprogs, classpath, util-linux-ng
OK, I've dug a bit more (sorry for all the breakage) and e2fsprogs /
classpath should be fine already, but not util-linux-ng (due to
modifying DEPENDS_virtclass-native). I've posted a patch I think will
fix this as it's a real problem and gettext.bbclass _should_ be a
replacement for DEPENDS = "gettext-native".
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-03-10 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 14:40 help2man-native: task configure fails with `configure: error: perl module Locale::gettext required` Paul Menzel
2011-03-10 15:04 ` Tom Rini
2011-03-10 15:40 ` Marco Cavallini
2011-03-10 16:07 ` Paul Menzel
2011-03-10 16:22 ` Peter Gsellmann
2011-03-10 17:40 ` Tom Rini [this message]
2011-03-10 16:39 ` Tom Rini
2011-03-10 15:24 ` Marco Cavallini
2011-03-10 15:25 ` Peter Gsellmann
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=4D790D04.5050409@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.