On Sat, Apr 14, 2001 at 04:32:14PM -0500, Joel Gwynn wrote:
> Until recently, I had a perfectly serviceable perl and mysql installation.
>
> Then, I was using the CPAN module, and it told me to install Bundle::CPAN.
>
> I did so, and now when I try to use my DBI module, Perl can't find it.
>
> I get the message:
>
> Can't locate loadable object for module DBI in @INC (@INC contains:
>/usr/local/lib/perl5/5.6.1/i686-linux /usr/local/lib/perl5/5.6.1
>/usr/local/lib/perl5/site_perl/5.6.1/i686-linux /usr/local/lib/perl5/site_perl/5.6.1
>/usr/local/lib/perl5/site_perl .) at DBI.pm line 180
> BEGIN failed--compilation aborted at DBI.pm line 180.
This is the one thing that I hate about CPAN.pm. It sees that certain
modules have more recent versions in a newer perl distribution, and
then installs a new perl for you.
Fairly recent versions make more and more of an attempt to separate
installed modules into version specific directories, which means that
a newly installed perl won't see them. (Older versions of perl left
more things in common directories, and it was harder to have to
simulaneous perl installations.)
I'd first suggest to see if there is a file named
/usr/local/bin/perl5.005, /usr/local/bin/perl5.6.0, or something
similar and move the /usr/local/bin/perl symlink to point to
the older perl.
I guess the next best suggestion would be to compare the files in
/usr/local/lib/perl and /usr/local/bin/perl* with the ones in your
last backup.
The next best thing would be to to save the old perl directory off
somewhere and then re-install the older perl using the same
Configuration options as you did last time.
If that didn't work, I'd then grab the old perllocal.pod from the old
perl installation and re-install them.
If that doesn't work, give another yell.
--
My imaginary friends told me about a really cool movie I want to see.
-- Samantha Langmead, age 3 1/2.
