>> So after about 2 solid days troubleshooting my Crypt::SSLeay problems here >> are some things that I learned that I hope can help someone else. >Thanks a lot! I really appreciate your effort. :-) > >> -M Net::HTTPS -M LWP -M LWP::Protocol::https is what worked. > >Interesting. Did ScanDeps fail to find even "LWP", when your script has >"use LWP::UserAgent"? It certainly works here.
-M LWP -M LWP::Protocol::LWPProtocol -M Net::HTTPS was what i actualy stopped testing with. >> I guess this was more of a problem with ScanDeps, I know very little about C >> and shared object loading, though I learned alot troubleshooting this. >Indeed. I have added LWP/Protocol/https.pm into ScanDeps's >heuristic base as a dependency to LWP::UserAgent, which should solve >your problem. Can you try installing: > >htttp://aut.dyndns.org/tmp/Module-ScanDeps-0.31.tar.gz > >and see if it works for you? If yes, I'll add your name to the AUTHORS >list and release it to CPAN. :-) > This new module works perfect. it compiled and ran with `pp -d --gui -o myprog.exe myprog.pl`; >> Autrijus is there a possible way to put some sort of debugging wrapper on a >> pp compiled executable that could perhaps throw "Module $Module not found", >> or "Shared Lib $so not found"? >You mean, making it non-fatal? LWP actualy caught the lack of LWP::Protocol::https in my script correctly(non fatal). I just never saw what it was looking for in the profiler/debuger, or error messages. I was wondering if there was a way to watch what module files a perl script was looking for and print out the search path, and module name if it didn't find it. I'll put some more thought into that, and perhaps propose a solution.
