On Tue, 3 Feb 2015 17:10:58 -0600 (CST)
"L. V. Lammert" <
lvla...@gmail.com> wrote:
> Excellent! Unfortunately, the writeup is about adding one's own
> module, .. What would correct PERL5LIB to remove the "local"?
>
> Where the compiled INC is /usr/local:
>
> /usr/local/lib/perl5/5.8.8/x86_64-linux
>
> and the system needs /usr/lib:
>
> /usr/lib/perl5/site_perl/5.8.8/local/
lib.pm
Q: Where does the perl binary you are running live?
The lib's your perl is configured to use at compile time should be
siblings of the bin directory your perl is run from. The system
perl will usually be in /usr/bin/perl, whatever you've installed
for your own use will live in /usr/local (BSD) or /opt (SYSV, linux).
At that point @INC will usually be based on something like
/usr/local/lib/perl or /usr/local/perl5/5.20.1/lib or /opt/lib
or /opt/perl5/lib.
At that point if you are trying to use modules that exist under
/usr/lib/perl5 from a binary run from /usr/local/bin then it
means you need to run you favorite CPAN interface to install them
where the perl binary is configured to find them.
Note: In general mixing your lib's with the system's is a bad idea.
Partly becuase the O/S lib's are infrequently updated and can have
security or operability problems, also because you cannot update
them without (a) su access and (b) possibly frying some piece of
the O/S code that is bug-compatible an ancient module.
--
Steven Lembark 3646 Flora Pl
Workhorse Computing St Louis, MO 63110
lem...@wrkhors.com +1 888 359 3508