- Although I didn't have any make program installed when i installed perl. perl -V:make tells me its nmake
- using winxp, activestate perl 5.8
- when i tried using the ppd file provided w/ win32-process from activestate, ppm tells me it can't find a suitable target for win32-process.
- nmake error is :
Microsoft (R) Program Maintenance Utility Version 1.50
Copyright (c) Microsoft Corp 1988-94. All rights reserved.
cp Process.pm ..\blib\lib\Win32\Process.pm
C:\Perl\bin\perl.exe -IC:\Perl\lib -IC:\Perl\lib C:\Perl\lib\E
+xtUtils/xs
ubpp -typemap C:\Perl\lib\ExtUtils\typemap -typemap typemap Process.x
+s >xstmp.c
&& C:\Perl\bin\perl.exe -MExtUtils::Command -e mv xstmp.c Process.cpp
cl -c -GX -nologo -Gf -W3 -MD -Zi -DNDEBUG -O1 -DWIN32 -D_CO
+NSOLE -DNO
_STRICT -DHAVE_DES_FCRYPT -DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS
+-DUSE_PERL
IO -DPERL_MSVCRT_READFIX -MD -Zi -DNDEBUG -O1 -DVERSION=\"0.09\" -
+DXS_VERSIO
N=\"0.09\" "-IC:\Perl\lib\CORE" Process.cpp
'cl' is not recognized as an internal or external command,
operable program or batch file.
NMAKE : fatal error U1077: 'C:\Windows\system32\cmd.exe' : return code
+ '0x1'
Stop.
edit will repost nmake error from work
| [reply]
[d/l]
[select] |
I think that Win32::Process is included in Activestate Perl 5.8, although I'm not sure. Try this:
perl -MWin32::Process -e 1
If you don't get any errors, you're good to go. This error 'cl' is not recognized as an internal or external command,
operable program or batch file.
means that you don't have a C compiler installed. When you install modules that have ".xs" components, you need a C compiler. Specifically, you need to use the same C compiler that was used to compile the particular 'perl' program you are using, in this case Microsoft Visual C++. The good news is that you can use the Standard or even, I think, the Learning Edition to compile XS modules. It's not too expensive.
| [reply]
[d/l]
[select] |