Hi there, having a problem with perl.
I get this error when trying to run any perl script.
###
Can't locate strict.pm in @INC (@INC contains: /usr/local/lib/perl5/5.8.0
BEGIN failed--compilation aborted at test line 2.
###
But I do not get the error when;
I am logged in as Root or,
I remove the line "use strict;"
I am actually running perl 5.6.1, I tried to install 5.8.0 a while back and it totally buggered my system and I had to restore from backup, but somehow it still see's the old perl.
If I do a perl -V I get this back,
@INC:
/usr/local/lib/perl/5.6.1
/usr/local/share/perl/5.6.
/usr/lib/perl5
/usr/share/perl5
/usr/lib/perl/5.6.1
/usr/share/perl/5.6.1
/usr/local/lib/site_perl/i
/usr/local/lib/site_perl
So @INC seems to know where to go.
This is very strange, I don't understand where perl is getting this info from, and why it only does it as a normal non SU user.
I removed all files pertaining to 5.8.0, there is nothing in my system for perl 5.8.
This was a Debian package install, I just reinstalled the latest copy and still get the error.
Does anyone know what is happening here?
Thanks for help.
-Air
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Check if after installing 5.8 you have the following directories
/usr/local/lib/perl/5.8.0
/usr/local/share/perl/5.8.
/usr/lib/perl/5.8.0
/usr/share/perl/5.8.0
If they are present then you can have two options:
[1] Change the @INC at compile time using 'lib' module
BEGIN { unshift(@INC, list of new directories to be added) }
[2] Change the variable "PERL5LIB" to point to the path for 5.8 in your profile file.
No, it should be owned by root, but readable by everyone. Which it is. Hey, I did say it was a shot in the dark. :)
However....
I just noticed something in your original question (which explains your comment about 5.8.0).
Try this as root.
# which perl; env | grep PERL; perl -V | tail
And again as non-root.
$ which perl; env | grep PERL; perl -V | tail
Perhaps there is more than one perl binary here, and/or root's environment is different than users' environment.
Do all of the following commands give the same results?
# /usr/bin/perl -V
# perl -V
$ /usr/bin/perl -V
$ perl -V
tomclegg, I had a friend helping a bit ealier and finally got by the problem. You were on the correct path with your last answer.
Turns out running as non su, Perl was using /usr/local/bin/perl and using su, perl was using /usr/bin/perl
But I checked the dates on /usr/local/bin/perl and found it to be the old 5.8 version, so looks like the debian package install won't write over this, so uninstalling wasn't an option, it would have removed 42 other packages, ouch, so I just recompiled 5.8.0 again, and boom, everything works now.
I am having a couple of module problems now with DBD::mysql but I don't think they are related to this.
I don't know why the debian package wouldn't just reinstall over this binary, oh well.
Thanks for your help though.
One point of clarification:
In Perl 5.8.5 and earlier "use strict;" was a pragma and strict.pm did not exist.
From Perl 5.8.8 on strict.pm DOES exist and the Perl interpreter will look for it if you "use strict;". But it's still pragma.
So you can hit the same problem when upgrading from versions of Perl 5.8.5 and earlier to versions of Perl 5.8.8 and later. Just make sure you whack any old versions of Perl and get your @INC paths right.
Business Accounts
Answer for Membership
by: tomcleggPosted on 2003-02-27 at 21:21:05ID: 8039536
Shot in the dark here. Try this (as NON-root user):
shell$ for d in /usr/local/lib/perl/5.6.1 \
/usr/local/share/perl/5.6.
/usr/lib/perl5 \
/usr/share/perl5 \
/usr/lib/perl/5.6.1 \
/usr/share/perl/5.6.1 \
/usr/local/lib/site_perl/i
/usr/local/lib/site_perl \
; do ls -ld $d >/dev/null && [ -e $d/strict.pm ] && ls -l $d/strict.pm; done
See if you get any "permission denied" errors. It's conceivable that strict.pm is only readable by root. I can't think why this would happen, but at least it's a nice easy thing to check. :)