Re: DBI.c has a problem

[hippo]

There is only one installation of Perl on this system.

If that's true then it appears that you have 2 separate DBI modules installed. Probably one from the package manager and one from CPAN. Find out which one works and then remove the problematic one.

[LanX]

Yes, and the OP could start comparing @INC for root and his user.

A diff should help narrowing the problematic path.

perl -MData::Dumper -E'say Dumper \@INC'

[K0ttn]

Hm, that was/is it. For some reason I have a /perl5/lib/perl5 library in my home directory. After some juggling, I was able to clean the @INC variable and it now runs. Thanks to all.

Jim

[LanX]

Honestly...

You should better address the root problem and uninstall the faulty DBI.pm instead of just excluding one path of @INC.

This will bite you sooner or later, in multiple ways.

[cavac]

As has been repeated on PerlMonks countless times: "Don't mess with system perl, install you own one on your home directory".

The reason is twofold:

1. If you mess up something in the perl installation provided by your operating system, you operating system mit not be able to work correctly or may even fail to boot properly.
2. Your operating system/package manager can update/change/remove/patch perl modules at any time, depending on the ever-changing dependencies of your installed programs. You don't want to spend hours trying to find a bug in your own programs, only to find out that your OS distributor did make some unofficial changes to some module.