On Mon, 10 Jun 2002, Automated Perl Test Account wrote: > -- > This is an error report generated automatically by CPANPLUS. > Below is the error stack during 'make test': > > PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" > "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t > t/*....t/*.t does not exist FAILED--1 test script could be > run, alas--no output ever seen > make: *** [test_dynamic] Error 2
I'm curious how the automated test script got to this point - manually, 'perl Makefile.PL' dies with an error that the string "@CPAN" must now be written as "\@CPAN". Does cpanplus generate a Makefile on its own if 'perl Makefile.PL' fails? If so, might it be better, if 'perl Makefile.PL' fails, to not proceed with automated testing until the reason for the failure is found? There might be a syntax error, as in this case, or the author may intentionally put in a die() if certain conditions aren't met (as would have been the case here, if neither GD nor Image::Magick is available). Using an automatically generated Makefile may omit or do things the author didn't intend. Fixing the above syntax error, a Makefile is generated, but with a warning that setting the abstract failed (this is because the NAME in Thumbnail.pm reports Image::Magick, not Image::Thumbnail). Running 'make test' then reports a similar error to the above - that's because there's a t/ subdirectory, but no *.t files in it (renaming t/*.pl to t/*.t, and doing away with test.pl, should fix that). [note to Lee - the automated test script of cpanplus prefers PREREQ_PMs for required modules, so maybe you could add such an entry for either GD or Image::Magick if neither is found]. best regards, randy kobes
