The reason that MakeMaker can't find Perl is because:
- $^X is returning "c:\\perl\\bin\\perl.exe"
instead of the usual "perl".
- The line of perl/lib/ExtUtils/MM_Win32.pm that reads
next unless $self->maybe_command($abs);
should really read
next unless $abs= $self->maybe_command($abs);.
Please do me a favor and use perlbug to report number 2
so it will be fixed (this saves me some time and gives
you a little practice in contributing to the community).
As for number 1, it might be something weird about
IndigoPerl or about the way you are executing
perl Makefile.PL. Perhaps you have a file
type association for *.PL and are just running
Makefile.PL which translates into
c:\perl\bin\perl.exe Makefile.PL, which
triggers the bug in MM_Win32.pm.
The DynamicState web site says that you'll need
DevStudio (aka Microsoft Visual Studio, including
Visual C++) to build modules that include XS code.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.