On 3/14/07, Dwight Oakey <[EMAIL PROTECTED]> wrote:
C:\Documents and Settings\doakey\My Documents\Perl>pp -o hello.exe -e "print qq[
INC = @INC\n];"
C:\Documents and Settings\doakey\My Documents\Perl>hello.exe
INC = C:\Temp\par-doakey\cache-48d2962a05347ff8390007247747db177006800a\inc CODE
(0xe38e88) CODE(0xe38fc0)
That one looks OK. BTW, does the above hello.exe work on the computer where
Validator2.exe fails?
>Does your script manipulate @INC in any way?
No. (see pp syntax below, though.)
But the INC in the error message suggests this - maybe some module behind
your back?
>Also, can you check whether a.exe correctly extracted PAR/Havey.pm?
>For that, locate the cache directory (should be something like
>%TEMP%\par-%USERNAME%\cache-SOME_WEIRD_HEX_NUMBER)
>and search it for a file that contains "package PAR::Heavy" (it's
>actually a copy
>of PAR/Heavy.pm, but with a weird name like 5856b869.pm).
Not in a file named as you claim; however, I do see an actual
inc/lib/PAR/Heavy.pm in this cache directory.
Strange, but happens sometimes.
Here's the syntax I'm using to run pp.:
C:\Documents and Settings\doakey\My Documents\Perl>pp --lib "C:\Inetpub_mercury\
sage\lib" --link LIBEXPAT.DLL -o Validator2.exe translation_content_validation_t
ool_gui.pl
As I understand it, ``--lib'' _adds_ to the library search path, it doesn't
replace it, right?
Yes. And it's only the path that pp uses to find the modules to pack in,
ie.it doesn't affect the path that the resulting executable has.
Puzzled, Roderich
