in reply to PAR-Packer and IPC-Run

So you have a program that runs in the Perl environment but not as an .exe. The most common cause of this is that some needed code hasn't been included within the .exe file. I would as a guess, add use Win32::Process before the use IPC statements. I don't have this version of run on my machine, can you say what Run.pm line 2143, line 2244 say?

Replies are listed 'Best First'.
Re^2: PAR-Packer and IPC-Run
by Anonymous Monk on Oct 11, 2023 at 05:19 UTC

    I tried including use Win32::Process and pp -M Win32:: without any luck.

    Line 2244 is an empty line. It's between two statements that are at the top of most of the subroutines: 

        &_assert_finished;

    my IPC::Run $self = shift;

    [download]
    And that subroutine doesn't appear to do anything too interesting. 
    sub _assert_finished {
    my IPC::Run $self = $_[0];

    croak "Harness not run" unless $self->{STATE} >= _finished;
    croak "Harness not finished running" unless $self->{STATE} == _fin
+ished;
}

    [download]
    Line 2143 is: $? = $kid->{RESULT} = 0x0F;

    There are commented line numbers that are exactly 1337 lines different from the actual line numbers, which seems intentional, but those just lead to another empty line and an array declaration. =/

[reply]
[d/l]
[select]

      Are you sure you are looking at the correct Run.pm ? There may be multiple instances of that file in your system ... you can always test by adding some debug message in it (perhaps just a die) and verify.

[reply]

In Section Seekers of Perl Wisdom