Figure out which of the test scripts failed. If, for example, it was "FAILED.t", then run: perl -Iblib/lib -Iblib/arch -d t/FAILED.t and single-step (via the debugger's "s" command) through the test script to see what is being tested, which ones are failing, and learn more details about why (the debugger's "h h" command gives a quick list of available commands and "perldoc perldebug" gives more information on debugging).

        - tye (but my friends call me "Tye")

In reply to (tye)Re: NMAKE : fatal error U1077: ‘C:\WINNT\system32\cmd.exe’ by tye
in thread NMAKE : fatal error U1077: ‘C:\WINNT\system32\cmd.exe’ by jamesluc

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.