how do you figured out what errors o fails?

I keep logs, run the failing tests by hand (  perl harness -v porting/buildtoc.t )

See Re: perl 5.14.0-RC1 is available for testing!

buildtoc is pod generation, the failure of the test doesn't impact generation of perltoc, and that is just a pod file ( list of =head from every pod file)

http://perl5.git.perl.org/perl.git?a=search&h=HEAD&st=free&s=buildtoc.t shows Rename t/porting/buildtoc.t to pod_rules.t, which calls http://perl5.git.perl.org/perl.git/blob/HEAD:/Porting/pod_rules.pl

update: after reviewing Re: perl 5.14.0-RC1 is available for testing! and pod_rules.pl, i don't see that the test actually tests anything of importance

In reply to Re^3: Failed building Perl on windows using Visual C++ 2010 by Anonymous Monk
in thread Failed building Perl on windows using Visual C++ 2010 by BAJA

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.