On 20/02/12 12:22, Dave Mitchell wrote:
On Mon, Feb 20, 2012 at 10:42:06AM +0000, Patrick Dupre wrote:
After an update fedora 13 to fedora 14, it looks like that perl has been
installed properly.
Linux teucidide 2.6.35.14-106.fc14.x86_64 #1 SMP Wed Nov 23 13:07:52
UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
This is perl 5, version 12, subversion 4 (v5.12.4) built for
x86_64-linux-thread-multi
but
perl -e 'foreach (@INC) {print "$_\n";}'
gives:
/usr/local/lib64/perl5
/usr/local/share/perl5
/usr/lib64/perl5
/usr/share/perl5
/usr/lib64/perl5
/usr/share/perl5
/usr/local/lib64/perl5/site_perl/5.10.0/x86_64-linux-thread-multi
/usr/local/lib/perl5/site_perl/5.10.0
/usr/lib64/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi
/usr/lib/perl5/vendor_perl
/usr/lib/perl5/site_perl
while I do expect:
/usr/local/lib/perl5
/usr/local/share/perl5
/usr/lib/perl5/vendor_perl
/usr/share/perl5/vendor_perl
/usr/lib/perl5
/usr/share/perl5
How can I fix the file Config.pm ?
You can't. The default search paths are hardcoded into the perl executable
at build time, so you'd have to rebuild the perl binary, or add a
BEGIN { @INC = qw(foo bar baz) }
at the top of each script.
But why do you want to do this? Although Fedora's choice of perl library
dirs is somewhat eccentric, is this actually causing you issues?
Note also that on 64-bit fedora, perl binary modules are stored under
/usr/lib64/perl5, so removing that from @INC would break your perl
installation.
Well I suppose the OP was/is worried about the apparent mismatch between
the two versions that appear in his post. I would suggest uninstalling
perl and then reinstalling it by yum or whatever; but again this is F14
and packages may not be easy to find.
John P
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
