before I run any test, should I 'rollback' any changes I've made (revert
PERL5LIB to its orginal value which was actually empty and also take the "if
Config.." out of parl.pl line 540?) so everything comes back to the
original state?
(since the modifications seem to have fixed it and maybe are masquerading
the original issue**)
On Wed, Jun 15, 2011 at 1:37 PM, Roderich Schupp <
roderich.sch...@googlemail.com> wrote:
> On Wed, Jun 15, 2011 at 11:38 AM, Nikos <nikos...@gmail.com> wrote:
> >>pp -o show_inc.exe -e "print qq[INC = @INC\n]"
> >
> > INC =
> >
> E:\DOCUME~1\LOCALU~1\LOCALS~1\Temp\par-LocalUser\cache-24fc4e15c702dfc458f
> > 533f99fd8ae8a8261ffb5\inc CODE(0x10cf89c) CODE(0x125fe94)
>
> That looks OK. But the problem occurs probably earlier in stage 2 of
> bootstrapping
> where @INC may have a different value...
> There's a diganostic script in the PAR::Packer tarball, can you run it like
> so
>
> perl contrib/extract_embedded/extract-embedded.pl any-pp-generated.exe
> some-scratch-directory
>
> (you may use the above show_inc.exe as the first argument) and post its
> output?
> Also: does show_inc.exe show the original symptoms ("Can't locate
> loadable object for module IO...")?
>
> Cheers, Roderich
>
