A) Should I try and find the author of the dependant module and ask for a sollution?
Nope, absolutely not. All you've shown us is that make failed, which is a pretty useless error message (you've managed to omit the more useful one).
B) Is there a way of finding out exactly what went wrong?
Yes, get rid of the intermediary(cpan) do a 'make realclean', and then report everything the make dance outputs (from perl Makefile.PL to make test) without omitting anything. You should also (for completeness) report the output of perl -V.
D) Is the test irrelevent and somehow 'forcing' it will suffice?
The test is always relevant, but forcing will sometimes suffice (it depends). There are a lot of poorly written tests out there, so you'll have to examine them and judge for yourself, but in my experience if the entire test suite is at least %90 ok, forcing is ok.

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

In reply to Re: linux modules cpan and things not found by PodMaster
in thread linux modules cpan and things not found by wolis

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.