Nope - this is XP Pro. And I'm definitely able to install software. Additionally, I have sucessfully installed several packages using the "perl Makefile.PL / nmake / nmake test / nmake install" combo.
-----Original Message----- From: Robert Davis [mailto:[EMAIL PROTECTED] Sent: Thursday, July 24, 2008 1:27 PM To: [email protected] Subject: RE: Can't Install PAR::Packer 0.980 > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Miller > Sent: Thursday, July 24, 2008 10:11 AM > To: [email protected] > Subject: Re: Can't Install PAR::Packer 0.980 > > On Thu, Jul 24, 2008 at 9:52 AM, Joe Fisher <[EMAIL PROTECTED]> wrote: > > Not really quite sure if this list also applies to PAR::Packer, but for > > some reason I can't get this module to install correctly. If I do > > 'nmake test', I always come up with: > > > > t/30-current_exec....# Please wait > > PAR::StrippedPARL::Static->get_raw() did not return the raw binary data > > for a PAR loader at blib\lib/PAR/StrippedPARL/Base.pm line 141, <DATA> > > line 1. > > Could not write temporary parl (class PAR::StrippedPARL::Static) to file > > 'C:\DOCUME~1\USER\LOCALS~1\Temp\parlv6hD.exe' at > > blib\lib/PAR/StrippedPARL/Base.pm line 65, <DATA> line 1. > > C:\Documents and Settings\user\Desktop\PAR-Packer-0.980\blib\script\pp: > > Failed to extract a parl from 'PAR::StrippedPARL::Static' to file > > 'parl5w7AXVr.exe' at blib\lib/PAR/Packer.pm line 1157, <DATA> line 1. > > > > I'm running ActivePerl v5.10.0 build 1002 [283697]. Can anybody help me > > with this problem? > > > > I don't see anything about this bug in the rt tickets. Personally, > I'd post something there about it. They're really good about fixing > things and adding features if there's enough information (and time). > > You know, ... flip through the tickets a little yourself though. Just > because I didn't see it doesn't mean it's not there. > > http://rt.cpan.org/Public/Dist/Display.html?Name=PAR%3A%3APacker > Is this vista? Sounds like a permission problem. Are you logged in as a administrator user?
