Don't use a local uncontrolled perl with a shared controlled module library path. You're asking for headaches, especially when combining modules with XS in them, crossing the 5.9 boundary (5.8 is not binary compatible with 5.10, there are probably other examples).
Instead, compile perl for your platform (linux/x86-64, it appears), and tell it that it will get installed to the shared filesystem. Make sure, too, that this shared filesystem is mounted the same on all machines (or symlinks make it seem that way). For example, /share/perl/5.8.8/{bin,lib}. Well, you should use something newer than 5.8.8 if at all possible. Then, use the shared perl instead of the local perl. Instead of #!/usr/bin/perl at the top of your scripts, use #!/share/perl/5.8.8/bin/perl. Mind you, this only really works if you have one platform. If you have multiple platforms, e.g., Linux and AIX or Sun or HP, or even Linux on x86-64 and Linux on x86-32, you'll probably want to install to platform-specific directories, have a shared library path, and then rely on the PATH to be set up properly to find the right perl.
Hope that helps.
In reply to Re: Need Help accessing perl modules installed on shared location
by Tanktalus
in thread Need Help accessing perl modules installed on shared location
by jainprithviraj
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |