[SOLVED] perl-core/Encode-2.40-r1 fails to emerge

[tony-curtis]

Code: Select all

 * Package:    perl-core/Encode-2.40-r1
 * Repository: gentoo
 * Maintainer: perl@gentoo.org
 * USE:        amd64 elibc_glibc kernel_linux multilib userland_GNU
 * FEATURES:   sandbox splitdebug
>>> Unpacking source...
>>> Unpacking Encode-2.40.tar.gz to /var/tmp/portage/perl-core/Encode-2.40-r1/work
>>> Source unpacked in /var/tmp/portage/perl-core/Encode-2.40-r1/work
>>> Preparing source in /var/tmp/portage/perl-core/Encode-2.40-r1/work ...
/var/tmp/portage/perl-core/Encode-2.40-r1/temp/environment: line 397: pushd: /var/tmp/portage/perl-core/Encode-2.40-r1/work/Encode-3.2.6: No such file or directory

I use "module" to manage extra software: the MODULE_VERSION environment variable it sets was being picked up and used by emerge.

[turtles]

I use "module" to manage extra software: the MODULE_VERSION environment variable it sets was being picked up and used by emerge.

I don't know what module is?
Do you mean cpan modules not in portage?
I think you should use g-cpan for that.

perl-core/Encode is in portage.
Did you upgrade perl and forget to run perl cleaner?

Try a

Code: Select all

 ls -la /usr/bin/perl

then

Code: Select all

ls /usr/lib/perl5/vendor_perl/

compare your versions of perl.
You may need to do an

Code: Select all

emerge -av1 perl

EDIT: and run

Code: Select all

perl-cleaner --all

Try doing an emerge --sync or eix-sync
then

Code: Select all

 emerge -avDN perl-core/Encode

[tony-curtis]

"module" as in http://modules.sourceforge.net/

It sets an environment variable called MODULE_VERSION: this was being used by portage and was misdirecting the build to a non-existent directory.

[turtles]

"module" as in http://modules.sourceforge.net/

It sets an environment variable called MODULE_VERSION: this was being used by portage and was misdirecting the build to a non-existent directory.

Wow neat.
I never herd of that.
Do you use it as a cross dev tool? or what for?

Did you get your Per Encode stuff to build?

[tony-curtis]

Yes, it builds.

"module" is to manage extra / different versions of packages, e.g. if you have extra compilers from various vendors, you can use module to add/remove PATH, MANPATH etc. settings.