Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

chaoticset (2105)

chaoticset
  (email not shown publicly)
http://chaoticset.perlmonk.org/
AOL IM: chaoticset23 (Add Buddy, Send Message)
Yahoo! ID: illuminatus_foil (Add User, Send Message)

JAPH. (That's right -- I'm not Really Inexperienced any more.)

I'm not just here, I'm here [perlmonks.org], and here [javajunkies.org] too, I ramble randomly in my philosophical blog [blogspot.com] and my other blog [blogspot.com]. Soon I'll come in a convenient six-pack.

Journal of chaoticset (2105)

Friday June 14, 2002
02:36 PM

Got Cocky, Acted Stupid

[ #5665 ]
...but then again, isn't that always the way?

"I learned my installation lesson! All I need is nmake and the same patient approach I used in RedHat, and I can install modules into my ActiveState perl build!"

Ha. Ha ha ha ha. Yeah, right.

I've never managed to properly install any module in Windows yet; either it's just a .pm module and I hand-craft an installation or else the PPM can handle it. I have just realized this.

One prompt open with the PPM, one open with the modules directory so I can attempt nmake for things that PPM barfs on. Crapola.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • If this is for work, get your boss to get you a copy of Visual C++. A properly configured version of that and a few GNU tools (gzip/gunzip binaries, tar binary, etc.) and you don't need PPM anymore -- just our friendly CPAN shell.