> I didn't copy the whole mailing list on this. Probably better to cc the list (trimming make verbosity is good then) since you can get more coverage and better response time. It has the additional benefit of putting the dialog in the record for people to search...
> Test Summary Report > ------------------- > t/autoload.t (Wstat: 256 Tests: 3 Failed: 1) > Failed test: 3 > Non-zero exit status: 1 > t/gsl_interp.t (Wstat: 65280 Tests: 10 Failed: 0) > Non-zero exit status: 255 > Parse errors: Bad plan. You planned 11 tests but ran 10. > t/proj_transform.t (Wstat: 65280 Tests: 0 Failed: 0) > Non-zero exit status: 255 > Parse errors: Bad plan. You planned 20 tests but ran 0. > Files=109, Tests=1195, 133 wallclock secs ( 0.60 usr 0.05 sys + 38.07 cusr > 2.01 csys = 40.73 CPU) > Result: FAIL >Failed 3/109 test programs. 1/1195 subtests failed. t/autoload.t: this is a false failure. You should be ok as is. t/gsl_interp.t: this seems to be related to pulling in the routine from another PDL version on the same system. Try making sure all the PDL-2.4.3 stuff is out of the shell PATH, and the @INC and PERL5LIB and run the test again. If you don't use the GSL you won't have a problem. t/proj_transform.t: this is usually because you are missing libjpeg or have an incomplete or outdated NetPBM install. If you don't use these functions, you should be good again. SUMMARY: Your PDL-2.4.4 should be ok to use (with the above caveats). You might wish to try out PDL-2.4.4_05 the next iteration as some of these have fixes and there are additional diagnostic outputs. Cheers, Chris
_______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
