Posting hundreds of lines of output from what you state was a successful Perl build (your first? congrats!)

Thousands dear boy! Thousands.

These are lines 9874 thru 9901 of the output from a "FAIL"d build -- one of hundreds over 15 years -- that runs everything I've thrown at it without error. 

Test Summary Report
-------------------
comp/multiline.t                                                (Wstat
+: 0 Tests: 6 Failed: 2)
  Failed tests:  5-6
io/dup.t                                                        (Wstat
+: 0 Tests: 23 Failed: 0)
  Parse errors: Tests out of sequence.  Found (8) but expected (2)
                Tests out of sequence.  Found (9) but expected (3)
                Tests out of sequence.  Found (10) but expected (4)
                Tests out of sequence.  Found (11) but expected (5)
                Tests out of sequence.  Found (12) but expected (6)
Displayed the first 5 of 23 TAP syntax errors.
Re-run prove with the -p option to see them all.
../cpan/Win32/t/GetShortPathName.t                              (Wstat
+: 0 Tests: 5 Failed: 1)
  Failed test:  2
../cpan/Win32/t/Unicode.t                                       (Wstat
+: 0 Tests: 11 Failed: 8)
  Failed tests:  1-3, 5, 8-11
  Parse errors: Bad plan.  You planned 12 tests but ran 11.
../dist/IO/t/io_dup.t                                           (Wstat
+: 0 Tests: 2 Failed: 0)
  Parse errors: Tests out of sequence.  Found (6) but expected (2)
                Bad plan.  You planned 6 tests but ran 2.
../dist/IO/t/io_sock.t                                          (Wstat
+: 13824 Tests: 25 Failed: 1)
  Failed test:  25
  Non-zero exit status: 54
  Parse errors: Bad plan.  You planned 26 tests but ran 25.
Files=2394, Tests=683435, 2113 wallclock secs (118.55 usr +  8.94 sys 
+= 127.49 CPU)
Result: FAIL
NMAKE : fatal error U1077: '..\perl.exe' : return code '0xc'
Stop.

[download]

As for "a bunch of bloviating blather": you are the master. I bow to your vexpertise.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^9: Perl-5.22.1 in ARM system (And yet expedient; and necessary!) by BrowserUk
in thread Perl-5.22.1 in ARM system by Anonymous Monk

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.