Hi, Thanks for creating the wonderful pp tool. I packaged an executable abc.exe from perl script using pp. Worked fine for most of users, But some users have existing old perl installation and have environmental variable PERL5LIB set. When these users run the abc.exe, they saw the following messages.
IO object version 1.21 does not match bootstrap parameter 1.23 at C:/programs/Perl/lib/DynaLoader.pm line 252. Compilation failed in require at C:/programs/Perl/lib/IO/Handle.pm line 263. BEGIN failed--compilation aborted at C:/programs/Perl/lib/IO/Handle.pm line 263. Compilation failed in require at C:/programs/Perl/lib/IO/Seekable.pm line 101. BEGIN failed--compilation aborted at C:/programs/Perl/lib/IO/Seekable.pm line 101. Compilation failed in require at C:/programs/Perl/lib/IO/File.pm line 133. BEGIN failed--compilation aborted at C:/programs/Perl/lib/IO/File.pm line 133. Compilation failed in require at -e line 313. =================== If the users put the following two lines in a dos bat file and doubleclick the bat file to run, and the abc.exe runs OK for all users. ==== abc_wrapper.bat == set PERL5LIB= ./abc.exe ================ So is there a way to package exe file to ignore the PERL5LIB environmental variable using pp ? If pp can do this, all users can get the exe file and run successfully independent of their environments. Even when users have old perl installation and have PERL5LIB set, uses can run the packaged exe without problem. This is extreamly useful for me and many pp users. ============= please help. Thanks a lot Henry Thanks !!
