Problem with 'test' in ActiveState's CPAN install

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

I'm a Windows Perl user, and I want to get to grips with CPAN. The CPAN module in ActivePerl looks like it'd be pretty useful, but every time I use it, I have the same problem. The output looks like this:

...lots of downloading...
Writing MakeFile for Foo::Bar
    -- OK
Running make test
'test' is not recognised as an internal or external command,
operable program or batch file.
   test -- NOT OK
Running make install
  make test had returned bad status, won't install without force
[download]

Anyone know what's wrong with my 'test'?

Thanks
Dennis

Comment on Problem with 'test' in ActiveState's CPAN install Download Code

Replies are listed 'Best First'.
Re: Problem with 'test' in ActiveState's CPAN install by rdfield (Priest) on Jan 20, 2003 at 16:02 UTC
If you want to install modules for Activestate, use ppm. CPAN installs require the use of a 'make' utility which is generally not present on a Windows box. Any modules not available from the usual archives (Activestate, theoryx5) generally have to be manually installed (ie unzip and manually copy the .pm files to the correct locations). rdfield	[reply]
Re^2: Problem with 'test' in ActiveState's CPAN install (no copying) by tye (Sage) on Jan 20, 2003 at 19:12 UTC
Please don't copy *.pm files by hand. (tye)Re2: Can't use Win32 Perl to FTP - no Net::FTP for Win32? contains pointers to and excerpts from standard documentation that comes with Perl that describes how to install modules. It also includes a working (I just retested it) link to download nmake.exe which is all you need on Win32 (besides Perl) to install any module that doesn't require a C compiler. - tye	[reply]
Re: Problem with 'test' in ActiveState's CPAN install by Jenda (Abbot) on Jan 20, 2003 at 20:32 UTC
You are using `make`, did you change the `C:\perl\lib\Config.pm`? ActivePerl was compiled with Microsoft Visual Studio, therefore the Config.pm references `nmake`! This means that the MakeMaker will generate a makefile compatible with `nmake`, but it doesn't have to work well with standard `make`. You may need to make more changes in Config.pm if you want to use a different compiler, not only make! Try to change the Config.pm and install the module once more. Jenda P.S.: There's another PPM repository at http://Jenda.Krynicky.cz/perl	[reply] [d/l] [select]