Again - with correction to silly mistake
Could you try the following test:
Open a command prompt.
Enter the following command:
set PATH=C:\Perl\bin;C:\Perl\site\bin;%PATH%
Then change directory to your script dir:
cd C:\Users\deadpickle\Desktop
Then check the pp version (do not put the full path to pp)
pp -V
Then try to package your test script
pp -o test.exe GRRUVI-windowed-v1.004.pl
What are the results?
Regards
Mark
Mark Dootson wrote:
Jamie,
Could you try the following test:
Open a command prompt.
Enter the following command:
set PATH=C:\Perl\bin;C:\Perl\site\bin;%PATH%
Then change directory to your script dir:
cd C:\Users\deadpickle\Desktop\GRRUVI-windowed-v1.004.pl
Then check the pp version (do not put the full path to pp)
pp -V
Then try to package your test script
pp -o test.exe GRRUVI-windowed-v1.004.pl
What are the results?
Regards
Mark
Jamie Lahowetz wrote:
I tried packing a test.exe using:
C:\Perl\site\bin>pp -o C:\Users\deadpickle\Desktop\test.exe
C:\Users\deadpickle\
Desktop\GRRUVI-windowed-v1.004.pl
and recieved this error:
parloQXY.exe - Entry Point Not Found: The procedure entry point
Perl_sv_2iv_flags could not be located in the dynamic link library
perl58.dll
And this in the terminal window:
Can't load 'C:/Perl/lib/auto/IO/IO.dll' for module IO: load_file:The
specified p
rocedure could not be found at C:/Perl/lib/XSLoader.pm line 64.
at C:/Perl/lib/IO.pm line 11
Compilation failed in require at C:/Perl/lib/IO/Handle.pm line 263.
BEGIN failed--compilation aborted at C:/Perl/lib/IO/Handle.pm line 263.
Compilation failed in require at C:/Perl/lib/IO/Seekable.pm line 101.
BEGIN failed--compilation aborted at C:/Perl/lib/IO/Seekable.pm line 101.
Compilation failed in require at C:/Perl/lib/IO/File.pm line 133.
BEGIN failed--compilation aborted at C:/Perl/lib/IO/File.pm line 133.
Compilation failed in require at -e line 405.
pp: Failed to extract a parl from 'PAR::StrippedPARL::Static' to file
'parl7zp57
i2.exe' at C:/Perl/site/lib/PAR/Packer.pm line 1149, <DATA> line 1.
Any help in this would be great.
On 8/21/07, Jamie Lahowetz <[EMAIL PROTECTED]> wrote:
The ActiveState Perl build I am using is 822. When installing PAR-Packer
using AS the files are automatically put in C:\Perl\site\bin. I added
this
to the windows path (assuming that is what you mean). It still will
not run
giving that pp is not an external command in cmd prompt. I did verify
that
pp.bat is in that directory and does exist. I may have to just
navigate to
the file to run pp.
--
Jamie Lahowetz