For a Win32 platform, your are far better off using the ActiveState Perl
port. While you are at their site (http://www.ActiveState.com/) read up on
PPM, too. Then use PPM to install the modules you want, it's much easier.
--
Mac :})
----- Original Message -----
From: Gregg Pace <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 03, 2000 10:08
Subject: Module Installation Problems
>. . .
>
>So, back on CPAN I go, I get Perl for DOS and get libwww-perl, written by
Gisle Aas.
>Reading the documantation for it, I find that I also need other modules -
>and they must be installed first. These modules are:
>
> URI
> MIME-Base64
> HTML-Parser
> libnet
> Digest::MD5
>
>So, back on CPAN I go. I get the modules listed. I then attempt to install
them.
>
>A lot of my problem is that I have just recently decided to move to Perl,
>and I really don't understand the installation of modules. I also don't
understand
>why a C make utility is needed, however I had one, and installed it where I
have
>Perl located.
>
>. . .
>
>By the way, the problem is not just with your package.
>I'm seeing the same type of errors installing other modules.
>
>I'm wondering if the backslash for DOS directories vs. the forward slash
for
>Unix directories is the problem.
Unless you are calling a program via system() or backticks, forward slashes
(/) work fine in Perl.
