laziness, impatience, and hubris | |
PerlMonks |
Re: Can't locate loadable object for module IO::Ttyby Perlbotics (Archbishop) |
on Jul 16, 2013 at 20:30 UTC ( [id://1044652]=note: print w/replies, xml ) | Need Help?? |
I would probably check...
HTH Update: The find-checks above are intended to detect typical access permissions problems. They only show files or directories in case the permissions are not set correctly. Ideally, files have permission 0644 or 0444 and directories and libraries (*.so, etc.) 0755 or 0555. There was a copy/paste error in the previous version of the code above, but now it is fixed without markup (lib and lib64 were swapped one time). Often, when installing modules under Solaris (don't know what you have, but I observed it there regularly), permissions get set too restrictively - the find rules above can be helpful there. Other permissions like 0440 might also cause failures but personally, I didn't encountered them in the wild, yet. If you can install your own Perl, do it as a non-root user (e.g. perl5). That fixed the situation (here - YMMV) and feels a little saver when installing stuff. Concerning PERL5LIB, if it is not set, you usually do not need to bother. Since you installed the modules in standard locations, there is no need to set this environment variable in order to fix the problem described. You can fix the permissions of perllocal.pod but it will not fix your original problem. It would just allow anybody to read the local installation history by means of perldoc perllocal - which is not a bad thing either. If it is not a permission problem, re-installation - as suggested by runrig - might be the easiest way to fix it.
In Section
Seekers of Perl Wisdom
|
|