Thank you very much for your help, I did not have nmake.exe and had no idea where to get it. I do decompress in a temp folder -- I just did not mention that step. "Jenda Krynicky" <Jenda@Krynicky.cz> wrote in message news:3C7A3554.18894.963BCDE@localhost... > From: "Thomas Whitney" <twhitney@centervision.com> > > > I am attempting to install a module on a Win2K machine using Active > > State Perl v5.6.0 build 615. > > > > I decompress the module and extract its contents to a new folder in > > \perl\site\lib. > > You should decompress it into a temporary directory, not to > ...\site\lib\something ! > > > Then in the command prompt I 'cd' into that new > > directory and type 'perl makefile.pl' --everything goes fine, there > > are no errors and a makefile is produced. > > > > Here is the problem: > > I type 'nmake' and I get: <'nmake' is not recognized as an internal > > or external command.> > > > > Note: I use 'nmake' because that is the result of "perl -V:make" > > ftp://ftp.microsoft.com/Softlib/MSLFILES/nmake15.exe > > Of course if the module contains any part written in C (erm ... XS) > you'll need a whole C compiler. Sorry I'm not sure which ones are > supported just now. > > Jenda > > =========== Jenda@Krynicky.cz == http://Jenda.Krynicky.cz ========== > There is a reason for living. There must be. I've seen it somewhere. > It's just that in the mess on my table ... and in my brain. > I can't find it. > --- meThread Previous | Thread Next