Re: [rt.cpan.org #116453] AutoReply: Prototype mismatch Windows 7 Strawberry Perl 24

"Malcolm via RT" <[email protected]>
Newsgroups gmane.comp.lang.perl.par
Message-ID <[email protected]>
Mon Jul 25 10:33:14 2016: Request 116453 was acted upon.
Transaction: Correspondence added by [email protected]
       Queue: PAR-Packer
     Subject: Re: [rt.cpan.org #116453] AutoReply: Prototype mismatch Windows 7 Strawberry Perl 24
   Broken in: (no value)
    Severity: (no value)
       Owner: Nobody
  Requestors: [email protected]
      Status: new
 Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=116453 >


The problem went away when I put the paths to Perl near the top of the 
environment variable path list.

Please close this ticket


On 7/25/2016 10:20 AM, Bugs in PAR-Packer via RT wrote:
> Greetings,
>
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding:
> 	"Prototype mismatch Windows 7 Strawberry Perl 24",
> a summary of which appears below.
>
> There is no need to reply to this message right now.  Your ticket has been
> assigned an ID of [rt.cpan.org #116453].  Your ticket is accessible
> on the web at:
>
>      https://rt.cpan.org/Ticket/Display.html?id=116453
>
> Please include the string:
>
>           [rt.cpan.org #116453]
>
> in the subject line of all future correspondence about this issue. To do so,
> you may reply to this message.
>
>                          Thank you,
>                          [email protected]
>
> -------------------------------------------------------------------------
> Windows 7, perl 5, version 24, subversion 0 (v5.24.0) built for
> MSWin32-x64-multi-thread
>
> F:\PAR-Packer-1.035>perl Makefile.PL
> Prototype mismatch: sub main::prompt: none vs () at
> C:/Perl/perl/lib/ExtUtils/MakeMaker.pm line 240.
> Generating a dmake-style Makefile
> Writing Makefile for PAR::Packer
> Writing MYMETA.yml and MYMETA.json
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.