Skip Menu |

This queue is for tickets about the Moose CPAN distribution.

Report information
The Basics
Id: 85550
Status: stalled
Priority: 0/
Queue: Moose

People
Owner: Nobody in particular
Requestors: JACKMANEY [...] cpan.org
Cc: jackmaney [...] gmail.com
AdminCc:

Bug Information
Severity: (no value)
Broken in: 2.0802
Fixed in: (no value)



CC: jackmaney [...] gmail.com
Subject: Unable to install Moose 2.0802 on Strawberry Perl (Win 7)
When trying to update Moose to the latest version (2.0802) on Strawberry Perl, I get the output in the attached text file. Within several C files (including Attribute.c, AttributeCore.c, Class.c, Generated.c, HasAttributes.c, HasMethods.c, et al) there are reports of undefined function references. I had initially thought that I needed to update gcc (the version that came with my mingw distribution was 4.5), so I upgraded gcc to 4.7.2. However, that didn't fix the issue. Although I'm slowly learning C and C++, I don't feel as though my skills in this area are up to par to be able to understand the entire Moose code base to figure out what's going on. Any help that you could provide would be much appreciated. Windows 7 Professional Edition Perl 5.16.3 (Strawberry Perl) gcc 4.7.2 Thank you for your time, Jack Maney jackmaney@gmail.com
Subject: moose_error_log.txt

Message body is not shown because it is too large.

On Wed May 22 16:18:47 2013, JACKMANEY wrote: Show quoted text
> When trying to update Moose to the latest version (2.0802) on > Strawberry Perl, I get the output in the attached text file. Within > several C files (including Attribute.c, AttributeCore.c, Class.c, > Generated.c, HasAttributes.c, HasMethods.c, et al) there are > reports of undefined function references. > > I had initially thought that I needed to update gcc (the version that > came with my mingw distribution was 4.5), so I upgraded gcc to > 4.7.2. However, that didn't fix the issue. > > Although I'm slowly learning C and C++, I don't feel as though my > skills in this area are up to par to be able to understand the > entire Moose code base to figure out what's going on. Any help that > you could provide would be much appreciated.
You'd probably have better luck asking Win32 Perl users/developers than the Moose team. AFAIK, none of use Perl on Windows regularly.