Barrie Slaymaker wrote:
I built a vcp.exe using a relatively recent PAR snapshot (which works
much better, thanks!) and a VCP user tried to run it on a machine with a
different Perl version.  He reports bug 4863 I entered a while ago:

http://rt.cpan.org/NoAuth/Bug.html?id=4863

I can reproduce it by building a foo.exe like so:

pp -o foo.exe foo.pl

where foo.pl is:

    use IO::Handler;
    print "hi\n";

and running it on a different VM with a different (older) ActiveState
perl installed.

IO.* are bundled in to foo.exe AFAICS:

    Z:\HostShare>wzunzip -v foo.exe | grep /IO\.
        469  DeflatN    317  33%  01/29/2004  22:19  9e5ba568 lib/IO.pm
          0  Stored       0   0%  12/09/2003  10:23  00000000 lib/auto/IO/IO.bs
      24645  DeflatN   5535  78%  12/09/2003  10:24  6e28c4ca lib/auto/IO/IO.dll
        696  DeflatN    352  50%  12/09/2003  10:24  f9748ddf lib/auto/IO/IO.exp

Z:\HostShare>

What can I do to help debug this?

- Barrie

----- Forwarded message -----

Hey Barrie,

I synced it down and gave it a go. Here's what I see when I run
it:

C:\Documents and Settings\yargle>vcp
IO object version 1.20 does not match bootstrap parameter 1.21 at
C:/Perl/lib/XSLoader.pm line 91.
Compilation failed in require at C:/Perl/lib/IO/Handle.pm line 260.
BEGIN failed--compilation aborted at C:/Perl/lib/IO/Handle.pm line 260.
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 117.
BEGIN failed--compilation aborted at C:/Perl/lib/IO/File.pm line 117.
Compilation failed in require at -e line 300.

Is it me or is it? =) Would like Perl version info or anything?

----- End forwarded message -----

Just upgraded to PAR 0.77. I'm getting the same problem here, too, but just by compiling any Perl program, such as simple a one-line "Hello World!" program, using pp with just the -o flag. This never happened in 0.75.


Using ActivePerl 5.8.0 on Windows 98 SE




Reply via email to