I'll be paying close attention to the answers about the proj lib
versions and further test output requested below.
I'm supposed to be the "better equipped" guy for the proj PDL interfaces
(I wrote them), but I don't have anything else to add to the questions
that Chris is asking at this time.
Let me know if there's anything I can do to help find or fix this
problem.
Thanks,
Judd Taylor
On Fri, 2008-11-14 at 07:41 -0500, Chris Marshall wrote:
> Hernán De Angelis wrote:
> >
> > First, I want to give warm thanks to all developers for the effort and
> > time in getting PDL 2.4.4 out!
> > Now, some doubts about test warnings and failures that I am having
> > right now just after downloading the last PDL version from CPAN. Using
> > openSUSE 11.0 on AMD Turion 64 X2, 2GB ram.
> >
> > 1.
> > t/pgplot....................Name "PGPLOT::HANDLE" used only once:
> > possible typo at
> > /usr/lib/perl5/5.10.0/x86_64-linux-thread-multi/DynaLoader.pm line
> > 226, <DATA> line 387.
> > (this test usually stops at 1712 or 7/12 and dies there. No clue why.
> > After CTRL+C and running again it appears again but the test passes.)
>
> Please try running from the PDL-2.4.4 directory:
>
> perl -Mblib t/pgplot.t
>
> to see if you can get more detailed failure information.
> It is also possible to run with the debugger to really
> trace where the problem is:
>
> perl -d -Mblib t/pgplot.t
>
> > 2.
> > t/proj_transform............Undefined subroutine &main::t_proj called
> > at t/proj_transform.t line 69, <PNM> line 3.
> > # Looks like your test exited with 9 before it could output anything.
> > t/proj_transform............ Dubious, test returned 9 (wstat 2304, 0x900)
> > Failed 20/20 subtests
>
> Again, please try running from PDL-2.4.4 directory:
>
> perl -Mblib t/proj_transform.t
>
> for additional diagnostic output. As above the debugger
> may also be used to localize the problem further. You
> need to be using a sufficiently current version of the
> PROJ4 libraries. Also, if you have multiple PROJ4 libs
> on your system, it is possible that the wrong ones are
> picked up.
>
> > and the report of all this is:
> >
> > Test Summary Report
> > -------------------
> > t/proj_transform (Wstat: 2304 Tests: 0 Failed: 0)
> > Non-zero exit status: 9
> > Parse errors: Bad plan. You planned 20 tests but ran 0.
> > Files=109, Tests=1131, 32 wallclock secs ( 0.75 usr 0.31 sys + 25.81
> > cusr 2.82 csys = 29.69 CPU)
> > Result: FAIL
> > Failed 1/109 test programs. 0/1131 subtests failed.
> > make: *** [test_dynamic] Error 255
> >
> >
> >
> > The good news is that if one runs "make install" anyway after the test
> > failure the demos run apparently OK.
>
> The demos don't test all features but the various PDL
> modules are pretty independent. In my experience, the
> functionality that passed testing can be used. The
> functions in the failed tests may still be mostly
> usable.
>
> It would be greatly appreciated if you could help
> track down these problems. The current plan for
> PDL releases is to have a developers release to
> CPAN so that fixes that accumulate will be available
> to the PDL community in a more timely fashion.
>
> Thanks for the feedback,
> Chris
>
> _______________________________________________
> Perldl mailing list
> [email protected]
> http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
>
--
____________________________
Judd Taylor
Software Engineer
Orbital Systems, Ltd.
3807 Carbon Rd.
Irving, TX 75038-3415
[EMAIL PROTECTED]
(972) 915-3669 x127
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
