Grygonos has asked for the wisdom of the Perl Monks concerning the following question:

I downloaded the zip wrapped tarball of libwin32 from cpan. I unzipped it to my \perl\build folder, and did makefile.pl

This worked fine...I then attempted nmake, it bombed. I tried another version of "win" make that I found via the gcc webpage and it said
Makefile:982: *** missing separator.  Stop.
the other error (from nmake)was long and non-descript really. Has anyone successfully installed this module and if so... how did you do it?

Replies are listed 'Best First'.
Re: trouble installing win32-process
by Thelonius (Priest) on Jul 21, 2003 at 21:22 UTC
    Most (maybe all) of the libwin32 modules are available as PPM modules at http://ppm.activestate.com/PPMPackages/, which is easier than building them.

    In fact, I think a lot of them are bundled with Activestate Perl, depending on which version you have.

    If you do need to build them, you must use nmake, not the gnu make, which gives the "missing separator" error.

    You didn't say:

    1. what version of windows you have
    2. what version of perl you have
    3. what version of nmake/MSC you have
    4. what happened when you ran nmake (other than "it bombed")
Re: trouble installing win32-process
by PodMaster (Abbot) on Jul 21, 2003 at 21:35 UTC
    You can't just pick a make program out of thin air. You have to use the make program your perl was built with. `perl -V:make' will tell you what it's called.

    MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
    I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
    ** The third rule of perl club is a statement of fact: pod is sexy.

Re: trouble installing win32-process
by barbie (Deacon) on Jul 21, 2003 at 23:59 UTC
    Oddly enough that 'missing separator' has been happening to me too. I've recently installed RH9 on my laptop and several modules have failed to load with that error, Compress::Zlib being one. I've been installing via 'perl -MCPAN -e shell;' so it should be using the default make.

    Curious.

    --
    Barbie | Birmingham Perl Mongers | http://birmingham.pm.org/

      • 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

        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.