On 18 May, 00:03, [EMAIL PROTECTED] (Mark Dootson) wrote: > pp -x -o prog.exe script.pl > > produces working exec from your test script in script.pl > > There are some dependencies missed by basic scan that -x option picks up. > > Regards > > Mark > > > > misoldgit wrote: > > On 17 May, 11:40, [EMAIL PROTECTED] (Steffen Mueller) wrote: > >> misoldgit schrieb: > > >>> Binary build 820 [274739] provided by > >>> ActiveStatehttp://www.ActiveState.com > >>> Built Jan 23 2007 15:57:46 > >>> ┌──────────────┬──────────┬─────────────────────────────────────────┬──────┐ > >>> │ name │ version │ abstract │ > >>> area │ > >>> ├──────────────┼──────────┼─────────────────────────────────────────┼──────┤ > >>> │ HTML-Parser │ 3.56 │ Parsing of HTML documents │ > >>> perl │ > >>> │ Math-Pari │ 2.010603 │ │ > >>> site │ > >>> │ PAR │ 0.90 │ Perl Archive Tookit │ > >>> site │ > >>> │ PAR-Dist │ 0.22 │ Create and manipulate PAR distributions │ > >>> site │ > >>> │ PAR-Packer │ 0.973 │ PAR Packager │ > >>> site │ > >>> │ Parse-Binary │ 0.10 │ │ > >>> site │ > >>> │ XML-Parser │ 2.34-r1 │ Parsing of XML documents │ > >>> perl │ > >>> └──────────────┴──────────┴─────────────────────────────────────────┴──────┘ > >> Whoa there! > > >> Before version 0.970 of PAR, PAR and PAR::Packer were both part of a > >> monolithic PAR package. Having PAR 0.90 and PAR::Packer 0.973 installed > >> at the same time is absolutely a problem. I.e. they both provide a pp > >> script, etc. > > >> If you installed PAR+PAR::Packer from a dependency-aware source (like > >> using the CPAN.pm client), the installer would have told you about this > >> problem and upgraded your PAR to the version required by the > >> corresponding PAR::Packer. > > >> It seems you installed PAR from the ActiveState PPM repository. That > >> repository is *severely* out of date regarding PAR. Can't blame them, > >> they sell a similar tool (PerlApp as part of their Perl Dev Kit). > > >> I suggest installing compatible versions of PAR and PAR::Packer such as > >> those from bribes.org. Note that I'm not saying that this will magically > >> fix all problems you might have with OpenPGP, but the setup as it stands > >> is *asking* for trouble. > > >> Cheers, > >> Steffen- Hide quoted text - > > >> - Show quoted text - > > > Hi guys, > > > OK I've tried to reply through this google interface twice now and it > > doesnt seem to take it - this may be due to the unicode text boxes > > that the new version of ppm puts round it's the module version output. > > > I have changed the version of Perl to 5.8.8.820 AND the versions of > > Par-packer etc per your instructions. It didnt seem to fix the > > problem. > > > BUT I think I've found the issue. The contents of @INC are different > > when the code is run natively to when it's run from the .exe: > > > When running the program .pl file: > > > @INC = C:/Perl/site/lib C:/Perl/lib . > > > When running the program via a .exe file: > > > @INC = C:\DOCUME~1\misoldgit\LOCALS~1\Temp\par-misoldgit > > \cache-1179417278/inc/lib C:\DOCUME~1\misoldgit\LOCALS~1\Temp\par- > > misoldgit\cache-1179417278/inc CODE(0xd5952c) . > > > So I manually re-assigned @INC to the correct paths within the program > > and voila! it works. > > > Guys, many thanks for all your help!- Hide quoted text - > > - Show quoted text -
Hmmm.. yes I think the @INC is a 'red herring' isnt it. If all of the required depndencies are included why is the script looking in the path so I agree with Mark's comment that there are extra dependencies that arent being picked up and when I run the -x flag as he suggests it does actually allow the test program to work (excellent) however the bad news is that when I use the -x flag on the 'real' program it fails with the same error (hohum). So my question really is, I guess, why isnt pp picking up all the dependencies from the get go and what is missing (do I have to manually add it). All of a sudden this is not so easy. Thanks (as always),
