Yes, as far as I can tell the environment is clean. No PERL or PAR
variables at all.
I can tell from a ProcMon log that it got as far as writing the
perl58.dll and the static binary. It successfully spawns the child
process and loads the linked system dlls and the perl58.dll from the
temp dire
On Mon, 08 Dec 2008, Scott Stanton wrote:
> This is a basic perl-5.8.8 distribution. ActivePerl has the same
> issue, but it checks two different locations (HKLM\Software\Perl and
> HKLM\Software\ActivePerl).
I don't think it uses HKLM\Software\ActivePerl for anything at runtime;
it is just the in
Hi David,
David Golden wrote:
> It's documented in 'perldoc perlwin32' so I think it's universal to Win32
> Perls. Suppressing it may be a question for p5p. Off the top of my head, I
> would think that if a packed app explicitly sets its own @INC, then the
> registry values would have no effect.
You have checked the obvious PERL5LIB environment var?
Scott Stanton wrote:
This is a basic perl-5.8.8 distribution. ActivePerl has the same issue,
but it checks two different locations (HKLM\Software\Perl and
HKLM\Software\ActivePerl).
After further investigation, I'm not sure this is really
This is a basic perl-5.8.8 distribution. ActivePerl has the same issue,
but it checks two different locations (HKLM\Software\Perl and
HKLM\Software\ActivePerl).
After further investigation, I'm not sure this is really the problem I'm
seeing, although it is a potential issue. The actual symptom i
On Mon, Dec 8, 2008 at 2:48 PM, Scott Stanton <[EMAIL PROTECTED]>wrote:
> It looks to me like Perl is searching in the registry under
> HKLM\Software\Perl and HKCU\Software\Perl for a number of values
> including any environment variable that starts with PERL, sitelib, and
> vendorlib. These all
Hi Scott,
Scott Stanton wrote:
> Has anyone else run into this before? Does anyone know of a way to
> suppress this behavior in Perl?
no, never. I agree it shouldn't happen in a PAR context. What
distribution of Perl is this originally?
Cheers,
Steffen
I'm running into a problem at a customer site where they appear to have
a conflicting install of Perl that is interfering with my PAR Packed
executable. My intent is for the packed program to be fully self
contained. I would prefer that it have nothing to do with any
previously installed Perl dis
