It is quite sad that the test harness actively hides the actual error message and replaces it with a bunch of details that are usually rather useless (and, IME, often actually incorrect).

If you learn how to do the rather simple steps to install a module without using all of the automation, then it becomes trivial to run t/01syntax.t directly so you can see the error message.

It looks like CPAN.pm is running App::Prove for you so you might be able to read enough documentation in order to figure out how to tell Prove to just show you all of the test results instead of summarizing them (badly) or some other way to get at the error message.

Maybe ExtUtils::Command::MM even documents its test_harness method.

Without the real error message, everybody is reduced to rather wild guessing just based on the fact that all of the tests are failing. So something is likely going wrong with just trying to load the module. Somebody who has seen a similar-looking failure can guess that something that they did might also work for you.

But I'd certainly go find the real error. Doing that is how one learns to diagnose problems which can be a very valuable skill to build, IME.

- tye        

In reply to Re: install fails for Inline::C (hide errors) by tye
in thread install fails for Inline::C by Special_K

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.