> As already mentioned I use Strawberryperl so dmake is what I use.

Yes, the build problem seems specific for dmake - CPAN test results show that 
*nix platforms are OK. It will be a few days until I will have time to dig 
further.

Cheers, Roderich

On 09.06.2010, at 10:28, Xaero <[email protected]> wrote:

> I'm sorry, i'm quite new to using a bug tracker, or usenet or even perl and 
> to programming in general. It looked liked the same issue i was having and so 
> I replied to it.
> 
> I don't think if I replied to the group Ulli would receive this message but 
> I'm not sure so: This is the sequece of commands I entered:
> ==
> cpan> upgrade PAR::Packer # from the cpan shell, since installation failed
> cpan> look PAR::Packer
> dmake
> dmake test #all test successful
> dmake install # install successful
> ==
> 
> As already mentioned I use Strawberryperl so dmake is what I use.
> 
> Regards.
> 
> On Tue, 8 Jun 2010 07:14:40 -0400
> [email protected] ("Roderich Schupp via RT") wrote:
> 
>> Tue Jun 08 07:14:39 2010: Request 57852 was acted upon.
>> Transaction: Correspondence added by [email protected]
>>       Queue: PAR-Packer
>>     Subject: Re: [rt.cpan.org #57852] install PAR::Packer failed for 
>> strawberry perl 5.12.0.1
>>   Broken in: (no value)
>>    Severity: (no value)
>>       Owner: Nobody
>>  Requestors: [email protected]
>>      Status: open
>> Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=57852 >
>> 
>> 
>> Folks, a bug tracker is NOT a discussion forum. Esp. if replying to a 
>> resolved bug will automatically re-open the bug (as is the case for 
>> rt.cpan.org).
>> PLEASE continue this discussion on the PAR mailing list [email protected]
>> 
>>> How did you run dmake twice?
>>> 
>> 
>> Go into the toplevel source directory and type "dmake"
>> 
>>> X:\perl>perl -v
>>> 
>>> This is perl, v5.8.8 built for MSWin32-x86-multi-thread
>> 
>> You're confused: this output indicates you're using ActiveState perl, not 
>> Strawberry. The former will most likely use nmake to build stuff.
>>> 
>> 
>> 
>> Cheers, Roderich

Reply via email to