Dying Makefile.PL is the last step :)
The referred example failed to loading the XS result without any information 
what failed.
A compiler or linker error would lead to broken make stage with output - so 
it's likely recommended to improve the tests (eg. by using C::AC ^^).

In doubt (no answer from a tester), one can easily add a test showing 
config.log on fail of module load ...

Am 08.12.2014 um 15:57 schrieb David Golden <x...@xdg.me>:

> To  minimize the amount of data that has to be transmitted and stored, only 
> output from the last step to run is generally sent.  So asking the tester or 
> adding .t files that dump diagnostic data are generally the best options.
> 
> David
> 
> 
> On Mon, Dec 8, 2014 at 3:14 AM, <sisyph...@optusnet.com.au> wrote:
> 
> 
> -----Original Message----- From: Tony Cook
> Sent: Monday, December 08, 2014 4:07 PM
> To: sisyph...@optusnet.com.au
> Cc: cpan-testers-discuss@perl.org
> Subject: Re: Viewing 'perl Makefile.PL' output of a test result
> 
> 
> On Mon, Dec 08, 2014 at 02:23:10PM +1100, sisyph...@optusnet.com.au wrote:
> Hi,
> 
> How do I view the output of the 'perl Makefile.PL' stage of a
> failing test report - eg for
> http://www.cpantesters.org/cpan/report/cc861d30-7e1e-11e4-b0eb-6fe8e0bfc7aa
> 
> Email the tester and ask politely for them to run it.
> 
> Oh, dear ... that's going to get tiresome real quick.
> I was hoping that the full build output would be recorded somewhere.
> 
> Thanks for the reply, anyway, Tony.

Cheers
-- 
Jens Rehsack
rehs...@gmail.com

Reply via email to