As you suggested, I put nmake in the path. I also moved the code file to a folder with no spaces in the name. And here is perl's response (which I will try to format correctly -- sorry about the last note).
C:\Temp\herehere>perl wma.txt
*****************
This module is deprecated. Please install the latest version of Inline
+X::C2XS instead
*****************
'nmake' is not recognized as an internal or external command,
operable program or batch file.
A problem was encountered while attempting to compile and install your
+ Inline
C code. The command that failed was:
nmake > out.make 2>&1
The build directory was:
C:\Temp\herehere\_Inline\build\wma_txt_8d90
To debug the problem, cd to the build directory, and inspect the outpu
+t files.
at wma.txt line 9
BEGIN failed--compilation aborted at wma.txt line 26.
C:\Temp\herehere
What should I look for in the output files? Other than that, I will gladly update the version of perl as you have suggested. Thanks.
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.