If you are building your own Perl from source, you should be able to find a solution. Unfortunately, it's been ages since I've done any of this, but as indicated here I used to build Perl (and many CPAN modules) from source on about 10 different Unix flavours and bundle it with our product in such a way that our product did not touch the customer /lib or /usr/lib. To achieve this (and to avoid the dreaded LD_LIBRARY_PATH), I'm pretty sure our install script binary-edited our executables, replacing their artificially long build PATH with the customer chosen install directory (with our lib sub-directory appended).
A few random nodes that might give you some ideas to try:
Sorry I can't be of more assistance just threw this out there in case it gives you some fresh ideas to try.
In reply to Re: Perl startup and excessive "stat" use on module load
by eyepopslikeamosquito
in thread Perl startup and excessive "stat" use on module load
by cherio
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |