Re^2: DBI.c has a problem

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'

Cheers Rolf
_{(addicted to the Perl Programming Language :)

see Wikisyntax for the Monastery}

Comment on Re^2: DBI.c has a problem Download Code

Replies are listed 'Best First'.
Re^3: DBI.c has a problem by K0ttn (Initiate) on Nov 24, 2024 at 17:31 UTC
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	[reply]
Re^4: DBI.c has a problem by LanX (Saint) on Nov 24, 2024 at 17:38 UTC
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. Cheers Rolf _{(addicted to the Perl Programming Language :) see Wikisyntax for the Monastery}	[reply]
Re^4: DBI.c has a problem by cavac (Prior) on Nov 25, 2024 at 12:51 UTC
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: 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. 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. PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP Also check out my sisters artwork and my weekly webcomics	[reply]