I haven't seen that sort of symptom before, but it looks like you might have more than one installation of DBI, and at least one of those installations seems to be incomplete.
The first thing I would try would be a test like this, to see where Perl is finding DBI-related stuff on your system:
perl -le 'for $p (@INC) {
print $p; opendir(P,$p);
print join("\n",grep /DBI/,readdir(P))}'
That comand line assumes a bash-like shell. If you are using the "default" ms-windows shell, just save the part between single quotes into a "test.pl" file, and do perl -l test.pl
Look at the dates of all the DBI-related files, and delete the ones that are older than the date of your most recent attempt to install the module. I'm not completely sure that it will help, but it's worth a try.
|