Hi,
Anyone managed to build 0.70 on ActiveState perl 5.6.1 ?
I have trouble doing it. I'm running build 626 - maybe the problem is with
that particular patchlevel build .... dunno.

And I don't *need* to have PAR running on  ActiveState perl 5.6.1, so it's
of little consequence to me, personally. (No problem on any of my other
Win32 perls.)

Running nmake proceeds ok until:
cl -c -Zm1000 -nologo -O1 -MD -DNDEBUG -DWIN32 -D_CONSOLE -DNO_STRICT -D
HAVE_DES_FCRYPT  -DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS -DPERL_MSVCRT_R
EADF
IX  -I"D:\Perl\lib\CORE" static.c
static.c

at which point it hangs. After a minute or so I got a pop-up informing me
that I was running low on virtual memory, at which point I killed it, which
produced:
NMAKE : NMAKE : fatal error U1058: terminated by user
Stop.
Compiler terminating.  Please wait.fatal error U1058: terminated by user
Stop.

and about twenty seconds later I got:
.......... Abort complete.

I note that progress has been made in cleaning up par's temporary directory.
All that's being left behind now is the *empty* directory
'par_priv.1224.tmp', 'par_priv.1328.tmp', etc. Can't be too far away from
cleaning that untidy feature up entirely :-)

Bit of a curiosity - I built an executable of a perl script that contained
only 'print $$;'. With 0.69, if the executable printed '1224', then the temp
directory would be called
 'par_priv.1224.tmp'. But with 0.70, the numbers no longer match.

Anyway, that's about it from me. That PAR works at all on *any* platform
still astounds me :-)

Cheers,
Rob





Reply via email to