in reply to how to install perlmodules in windowsXP

nmake is not bundled with on XP. You can download it from Microsoft directly, by consulting KB Article 132084. This is probably simpler than going the whole MinGW route, and less alpha than Strawberry Perl.

As a side note, nmake is not capable of understanding the current Makefile used to build the latest bleadperl (what will one day be 5.10). For that, you will need to use dmake. (Clarification following private correspondance: any version of MSVC released this decade or thereabouts will be just fine).

• another intruder with the mooring in the heart of the Perl

  • Comment on Re: how to install perlmodules in windowsXP

Replies are listed 'Best First'.
Re^2: how to install perlmodules in windowsXP
by veeruch (Sexton) on Mar 05, 2007 at 11:57 UTC
    still iam getting this error while iam doing nmake test

    cl -c -I.. -I../pTk/mTk/xlib -I. -Ibitmaps -I../pTk/mTk/xlib -nologo -GF -W3 -MD -Zi -DNDEBUG -O1 -DWIN32 -D_CONSOLE -DNO_STRICT -DHAVE_DES_FCRYPT -DNO_HASH_SEED -DUSE_SITECUSTOMIZE -DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS -DUSE_PERLIO -DP ERL_MSVCRT_READFIX -MD -Zi -DNDEBUG -O1 -DVERSION=\"804.0275\" -DXS_VERSION=\"804.0275\" "-IC:\Perl\lib\CORE" ClientWi n.c 'cl' is not recognized as an internal or external command, operable program or batch file. NMAKE : fatal error U1077: 'C:\WINNT\system32\cmd.exe' : return code '0x1' Stop. NMAKE : fatal error U1077: 'C:\WINNT\system32\cmd.exe' : return code '0x2' Stop. <error>
      You are trying to install a module that has an XS-Extension / includes C-Code. You need to get a C compiler or install the module via PPM.


      holli, /regexed monk/
Re^2: how to install perlmodules in windowsXP
by syphilis (Archbishop) on Mar 06, 2007 at 05:24 UTC
    You can download it from Microsoft directly, by consulting KB Article 132084

    That's a fairly old and crappy version of nmake. For building perl modules it will mostly work - but there are exceptions (eg PDL) for which a more recent version of nmake is required.

    I think the reliability of that version of nmake is a much bigger worry than the alpha status of Strawberry Perl.

    any version of MSVC released this decade or thereabouts will be just fine

    Well .... if you want to use a Microsoft Compiler with ActiveState Perl, then the best one to use is version 6.0 - since that's the compiler used to build ActiveState Perl. All later Microsoft Compilers use a different runtime library - and that is something that can bite you. Otoh the MinGW compiler uses the same runtime library as MSVC-6.0 - which is one thing in its favour when it comes to getting a free C compiler to use with ActiveState Perl.

    When I look at the questions the OP has asked, I can't help but wish he had simply installed Strawberry Perl to begin with. It gives you the make (dmake) utility and the C compiler - nothing to configure, and no questions to ask. All you really then need to do is install the ppm module from CPAN and you also have immediate access to the wide range of ppm packages - for any modules that you have trouble building. It just doesn't get any simpler ...

    Cheers,
    Rob