public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Stuge <peter@stuge.se>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] I need generic solution to package non-building uder catalyst...
Date: Wed, 8 Jan 2014 20:30:04 +0100	[thread overview]
Message-ID: <20140108193004.24874.qmail@stuge.se> (raw)
In-Reply-To: <CACU8XW=1Uj_ReV74UGYhEWsK=8oPDPGWfDs1f8VS4fe+GkB_pA@mail.gmail.com>

lin pro wrote:
> This time it is about help2man requiring Locale_gettext pearl
> module package.
> The message in itself is very simple and clear. There is no
> dev-utils/Locale_gettex  available for emerge durring the configure
> phase.

At first that might seem like a bug in the help2man ebuild.

However,

RDEPEND="dev-lang/perl
        elibc_glibc? ( nls? (
                dev-perl/Locale-gettext
        ) )"

..the dependency looks fine, meaning that dev-perl/Locale-gettext
is in fact installed on your system.

The problem may be that perl has been upgraded, perhaps as a result
of using a newer portage tree for the stage4 than the stage3 was
built with, but perl modules haven't been upgraded to be availble in
the new version of perl.

Either chroot into the stage4 temp dir as already described, or hack
the catalyst stage4-chroot.sh script to run perl-cleaner --all right
after run_merge -uav system.


> My question is hwo to tacke those problems from within catalyst.

Avoid the problem by building a full set of stage1, stage2, stage3
and stage4 using only one specific portage tree.


//Peter


  parent reply	other threads:[~2014-01-08 19:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08  0:57 [gentoo-catalyst] I need generic solution to package non-building uder catalyst lin pro
2014-01-08  1:09 ` [gentoo-catalyst] " W. Trevor King
2014-01-08 17:51   ` lin pro
2014-01-08 17:59     ` W. Trevor King
2014-01-08 19:30 ` Peter Stuge [this message]
2014-01-09  2:56   ` [gentoo-catalyst] " Jorge Manuel B. S. Vicetto

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=20140108193004.24874.qmail@stuge.se \
    --to=peter@stuge.se \
    --cc=gentoo-catalyst@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox