Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number
 
PerlMonks  

Re^5: Using CPAN

by dasgar (Priest)
on Dec 02, 2013 at 10:30 UTC ( [id://1065274]=note: print w/replies, xml ) Need Help??


in reply to Re^4: Using CPAN
in thread Using CPAN

I'm not familiar with Watcom. Based on a Google search, I'm guessing that you're referring to Open Watcom.

The primary two compiler's that I personally have heard of being used on Windows to compile Perl and Perl modules is Microsoft's Visual Studio and MinGW, but that's not to say other compilers couldn't be used.

Regardless of which compiler you choose to go with, it (and its utilities, like make) must be compatible with the compiler used to compile your Perl installation. You said that you were using ActiveState's ActivePerl. If you're using the 32-bit version, you should use the PPM utility to install MinGW and dmake from ActiveState's repository. Those are guaranteed to work. If you're using the 64-bit version, I think there may be a few more steps and other things to be concerned about.

If you want an alternative, here's my suggestions:

  • Try using the PPM utility to install from ActiveState's repository, which someone else has suggested a few times. That method does not involve you needing a compiler on your system.
  • Try Strawberry Perl, which comes with everything you need. They also have a portable version available.
  • I personally haven't used it, but I've seen others recommend Citrus Perl.

By the way, is "MinGW64-4.5.4" the 64-bit version? If so, that may be another issue. In your OP stated that you're using "Win7 (x86)". Forgetting everything else, installing (or trying to install) any 64-bit application on a 32-bit OS isn't going to work.

Replies are listed 'Best First'.
Re^6: Using CPAN
by Anonymous Monk on Dec 02, 2013 at 10:50 UTC
Re^6: Using CPAN
by LloydRice (Beadle) on Dec 03, 2013 at 06:41 UTC

    Yes, I was referring to Open Watcom. It's very possible that there are conflicts between that compiler and MS or MinGW. I just renamed 'make', but there could be other names in common. Perhaps I could try renaming the Watcom installed directory. But I do use that compiler frequently, so it's a bit of a hassle to kill it, even temporarily.

    I did try using PPM to install Imager. That produced the same errors as before.

    I was wrong in adding 'x86' to the machine spec. It is a 64-bit machine which, under Win7, can run either x86 (32-bit) or 64-bit code.

      I again tried perl ppm Imager and this time, everything worked as expected. I'm off and running. Thanks to all.

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://1065274]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others wandering the Monastery: (4)
As of 2024-03-28 16:59 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found