[The OP was updated to indicate that this was a non-system perl after my post.] I am hoping that you did not move the system perl to another location.
A perl installation that is not explicitly relocatable is compiled with certain paths embedded in its configuration. You may be able to hack some changes into the Config.pm module (ick ick ick - read: RISK), but I would agree with others that the best option is to do a rebuild for your platform.
Also, if you are currently using the system perl for an application, and installing your own modules into that system perl, and upgrading the installed modules in the system perl, STOP. Install your own version of Perl to use with your homegrown applications. The system expects a certain perl environment, and messing with it is setting the operating system up for failure -- not a good thing. Additionally, you are tying your application to the OS vendor's whims as to what an acceptable version of Perl and modules happens to be.
Uncouple your application from the OS's perl installation, and take control of the environment it runs within.
Update: added OP update note
|