Perl lib version (v5.8.8) doesn't match executable version (v5.8.3)

Posted by WingedRaptor on 2007-04-16 07:20

I recently had to reinstall ActivePerl on this computer after I seemingly broke it trying to get DBI/DBD to install properly. After doing so, I got the following error:

Perl lib version (v5.8.8) doesn't match executable version (v5.8.3) at D:/Perl/lib/Config.pm line 46. Compilation failed in require at D:/Perl/lib/Time/Local.pm line 5. BEGIN failed--compilation aborted at D:/Perl/lib/Time/Local.pm line 5. Compilation failed in require at (eval 2) line 2. BEGIN failed--compilation aborted (in cleanup) Perl lib version (v5.8.8) doesn't match executable version (v5.8.3) at D:/Perl/lib/Config.pm line 46. Compilation failed in require at D:/Perl/lib/Time/Local.pm line 5. BEGIN failed--compilation aborted at D:/Perl/lib/Time/Local.pm line 5. Compilation failed in require at (eval 2) line 2. BEGIN failed--compilation aborted

PDK hasn't been installed on this system, so the official fix doesn't do me much good. I've reinstalled AP several times after removing whatever trace elements of Perl on my system I could find, but I still keep getting version mismatches.

Also, commenting out 'use time::local' just nets me more errors for whatever the next module in line is. Anyone have any ideas about where the conflicting Perl files might be located or if there is an archive of older Windows binaries?

Technically, some of the old packages exist (as a backup), but in a renamed/moved folder. Would the new AP install be able to try to use those older packages regardless of their new location?

WingedRaptor | Wed, 2007-04-18 06:15

A small update on my predicament. It seems that these errors are specific to the ASP implementation of Perlscript rather than ActivePerl itself. I can run solo scripts just fine through cmd while using the exact same modules and functions, but my ASP page simply gives the previously quoted error.

Anyone have any ideas?

WingedRaptor | Wed, 2007-04-18 08:01

As always, the simplest of solutions had evaded me. All I forgot to do after removing all residual files from my system was to reset the computer before reinstalling Perl. That's what I get for not following the golden rule of IT, "Have you tried turning it off and on again?"

kevinw
ActiveState Staff
Wed, 2007-04-18 15:34

Good to hear you got it going! Thank you for posting the solution -- that will no doubt help anyone in the same situation.

Cheers,

kjw