From: Harry Putnam <reader@newsguy.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: perl versioning problem, how to get beyond for @world
Date: Fri, 25 May 2012 14:06:49 -0400 [thread overview]
Message-ID: <8762bkrv7q.fsf@newsguy.com> (raw)
In-Reply-To: CA+2pebtjuBJ+B+60s9-oUtCs+kNjUYFSnBA+NWx4bYRMjopMhg@mail.gmail.com
"Arttu V." <arttuv69@gmail.com> writes:
> It looks like the @INC list (the directory list perl uses for finding
> its modules) is not right or is not processed right. Only one
> directory is looked into? (You can see @INC with "perl -V", it should
> be up to about ten directories on a Gentoo install.)
Doesn't seem to have been related to @INC as that variable contains
all the usual suspects. Far as processing that may be the problem.
> Unless you really, really want to know exactly which bit from which
> package is sideways you might get out of the hole simply with:
> perl-cleaner --reallyall
Thanks for that.
I did `perl-cleaner --reallyall' but the emerge process engendered by it
failed again at the same perl module: perl-core/Module-Build-0.400.0
------- --------- ---=--- --------- --------
Here is what seems to have fixed things up... I'm not sure if all of
it is required, but what I finally did was unmask the hard mask on
perl-5.14
Emerged that with -uD flags which caused the same troublesome
perl-core/Module-Build-0.400.0 to be installed after the new perl was
installed and it went by without a whimper.
Then followed with perl-cleaner --all, followed by revdep-rebuild.
(neither of those seemed to find much to do).
Apparently the perl change was fully cleaned up during install so
perl-cleaner had nothing to do.
And finally `eix-sync' followed by `emerge -vuDp @world' which revealed
that those troublesome perl modules: perl-core/Module-Build-0.400.0
and Parse::CPAN::Meta are now not coming up since they are installed.
However I see a new gcc in the output so thinking I'll install that by
itself and set the new one up as active before doing `emerge -vuD
@world'
I'll post this once I see if a full emerge -vuD @world works without failure.
tic toc . tic toc ....
OK, the full `emerge -vuD @world', followed by `revdep-rebuild' has
gone down trouble free.... all fixed I guess.
prev parent reply other threads:[~2012-05-25 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 22:58 [gentoo-user] perl versioning problem, how to get beyond for @world Harry Putnam
2012-05-14 23:21 ` Alan McKinnon
2012-05-18 1:03 ` [gentoo-user] " Harry Putnam
2012-05-21 18:42 ` Arttu V.
2012-05-25 18:06 ` Harry Putnam [this message]
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=8762bkrv7q.fsf@newsguy.com \
--to=reader@newsguy.com \
--cc=gentoo-user@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