I'm not very well versed in the use of PP, either :) In particular, I'm not sure how far (i.e. up to what recursion level) it would go to resolve and automagically include all secondary library dependencies, in order to create a fully self-contained package.
In your case, it looks as if the Oracle lib libclntsh.so is either missing, or - in case it is actually included - the dynamic loader is not instructed properly (via LD_LIBRARY_PATH or some such) to load the right lib. libclntsh.so is a dependency of the DBD::Oracle module — most likely not the only one though... Running ldd on the respective .so file belonging to DBD::Oracle should show the full list of dependecies. Those would have to be included/distributed with the package (unless you can make sure by other means that they're already installed on the target system (and the versions match, etc.)).
I'm afraid I can't tell you precisely what to do to fix the issue, but hopefully this gives you some clue where to start digging in the PP docs... Maybe you just need to somehow tell PP about the directory where the proper libclntsh.so etc. are kept (see ldd output), so it does include those libs, too (?). I would start playing with PP's option --link, or maybe -a plus manually fixing LD_LIBRARY_PATH from within your script (so the added lib files will be looked for wherever you put them...). Good luck anyway!
In reply to Re: PP problems finding DBI driver libraries
by almut
in thread PP problems finding DBI driver libraries
by OedipusPrime
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |