http://www.perlmonks.org?node_id=378669


in reply to Re: A Guide to Installing Modules
in thread A Guide to Installing Modules

Without being too rude the whole idea of this tutorial was to teach you how to install a Module by hand. PPM and CPAN are convenience tools. Like all tools they have issues. You have just found one.

Go to search.cpan.org. Type in Win32::RASE, search, download the module, extract it (winzip will do). While you are there type in 'enum' - this is another module (enum.pm), so do likewise - download and extract it as well.

Now get a command prompt. Navigate to dir where you extracted the modules to (I extract into c:\temp) so cd c:\temp\[module name] will do it. Follow instructions above ie perl Makefile && nmake && nmake test && nmake install

If you try to do RASE first you will note it says it needs enum.pm (that's why you got it) so do that first and RASE second. It is very easy and should take no more that a couple of minutes.

If you want the docs (from the pod) to appear in the ActiveState docs do one of these after you have installed the modules.

# probably this perl -MActivePerl::DocTools -e ActivePerl::DocTools::UpdateHTML() # if not this should do it. perl -MActivePerl::DocTools -e ActivePerl::DocTools::WriteTOC()

cheers

tachyon

Replies are listed 'Best First'.
Re^3: A Guide to Installing Modules
by wfsp (Abbot) on Jul 30, 2004 at 16:25 UTC
    Sorry for missing the point of your tutorial and thanks for your patience and reply.

    Enum appeared to install ok as follows:

    C:\enum\enum-1.016>perl makefile.pl Checking if your kit is complete... Looks good Writing Makefile for enum C:\enum\enum-1.016>nmake WARNING: missing nmake.err; displaying error numbers without messages +. cp enum.pm blib\lib\enum.pm C:\enum\enum-1.016>nmake test WARNING: missing nmake.err; displaying error numbers without messages +. C:\Perl\bin\perl.exe "-MExtUtils::Command::MM" "-e" "test_harness(0, ' +bl ib\lib', 'blib\arch')" t\dot_dot.t t\new_index.t t\new_package.t t\new +_tag.t t\s imple_tags.t t\dot_dot........ok t\new_index......ok t\new_package....ok t\new_tag........ok t\simple_tags....ok All tests successful. Files=5, Tests=14, 0 wallclock secs ( 0.00 cusr + 0.00 csys = 0.00 +CPU)
    It installed itself here:
    Directory of C:\perl\site\lib\win32\ole 01/06/2004 12:15 2,839 Enum.pm 1 File(s) 2,839 bytes 0 Dir(s) 8,706,207,744 bytes free
    But installing Win32::Rase produced:
    C:\win32-RASE\Win32-RASE-1.01>perl makefile.pl Checking if your kit is complete... Looks good Warning: prerequisite Win32::API 0 not found. Warning: prerequisite enum 1.014 not found. Writing Makefile for Win32::RASE
    Is the difference between enum 1.014 and enum 1.016 significant?

    I noticed that Win32::API was also not found.

    I have Win32API::File, Win32API::Net and Win32API::Registry. I downloaded Win32::API from CPAN.

    C:\Win32-API-0.41>perl makefile.pl Checking if your kit is complete... Looks good Writing Makefile for Win32::API::Callback Writing Makefile for Win32::API C:\Win32-API-0.41>nmake Microsoft (R) Program Maintenance Utility Version 1.50 Copyright (c) Microsoft Corp 1988-94. All rights reserved. cp Type.pm blib\lib\Win32/API/Type.pm cp Callback.pm blib\lib\Win32/API/Callback.pm cp Struct.pm blib\lib\Win32/API/Struct.pm cp API.pm blib\lib\Win32/API.pm C:\Perl\bin\perl.exe C:\Perl\lib\ExtUtils/xsubpp -typemap C:\ +Perl\lib\E xtUtils\typemap Callback.xs > Callback.xsc && C:\Perl\bin\perl.exe -M +ExtUtils:: Command -e mv Callback.xsc Callback.c cl -c -nologo -Gf -W3 -MD -Zi -DNDEBUG -O1 -DWIN32 -D_CONSO +LE -DNO_ST RICT -DHAVE_DES_FCRYPT -DNO_HASH_SEED -DPERL_IMPLICIT_CONTEXT -DPERL_I +MPLICIT_SY S -DUSE_PERLIO -DPERL_MSVCRT_READFIX -MD -Zi -DNDEBUG -O1 -DVERSION +=\"0.41\" -DXS_VERSION=\"0.41\" "-IC:\Perl\lib\CORE" Callback.c '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. NMAKE : fatal error U1077: 'C:\WINDOWS\system32\cmd.exe' : return code + '0x2' Stop.

    Does this mean I need a C compiler?

    Sorry to be a pain.

    Note: I found and moved nmake.err into the path.

      I don't know why Enum.pm installed in the wrong location, actually I am almost certain it did not. The module you are installing is enum.pm not Enum.pm for a start. Did you do the nmake install? When I do it this is what it says.....

      [snip, following the tests we do.....] C:\enum-1.016>nmake install Microsoft (R) Program Maintenance Utility Version 1.50 Copyright (c) Microsoft Corp 1988-94. All rights reserved. Skipping D:\Perl\site\lib\enum.pm (unchanged) Writing D:\Perl\site\lib\auto\enum\.packlist Appending installation info to D:\Perl\lib/perllocal.pod C:\enum-1.016>

      So you can see where it goes. You can just cut and paste the enum.pm module to \perl\site\lib\enum.pm and it will work but I am certain you forgot the install step as on my system there is enum.pm as noted and Enum.pm in Win32\OLE\Enum.pm :-)

      Don't know why you don't have Win32::API if you have ActiveState Perl (you did say you were using ppm). cl is the M$ C compiler and you do need it to compile source that contains C. I have a tutorial on setting that up as well but you need access to MSVCC. However Win32::API is available as a ppm so all you need to do is:

      C:\>ppm install Win32::API Installing package 'Win32-API'... Downloading http://ppm.ActiveState.com/PPMPackages/5.6plus/MSWin32-x86 +-multi-thread/Win32-API-0.41.tar.gz ...

      cheers

      tachyon

        Phew! I've installed a module from CPAN and used it to dialup a connection!

        I was sure that Re: Installing Perl on a Windows PC was wrong. Now I'm not so sure. As soon as I get under the bonnet it's like a big black hole.

        I did notice this though:

        C:\Win32-RASE-1.01>nmake test Microsoft (R) Program Maintenance Utility Version 1.50 Copyright (c) Microsoft Corp 1988-94. All rights reserved. C:\Perl\bin\perl.exe "-Iblib\lib" "-Iblib\arch" test.pl 1..6 ok 1 not ok 2 ok 3 ok 4 ok 5 not ok 6
        Is it safe to ignore?

        Many thanks for your help
        btw, I thought your black hole looked a bit white!