#18 detect multiple PDL installs on build


A user reported a problem building PDL on their system
with two test failures. The issue was that the two PDL
modules related to the tests had not been built since
the needed gd and GSL libraries were not installed.

The test still tried to run because the system apparently
had another version of PDL installed in the main perl5
library location. This was detected when the use check
was performed at the start of the test.

Ideally, we could use the PDL::Config information to
have tests skipped that have not been configured or
build. Another possibility would be to detect the
out-of-blib-tree location in the test runs


  • Chris Marshall

    Chris Marshall - 2010-02-20

    I note that Module::Build appears to have a method for checking for pre-existing
    installs which may be useful to detect this problem.

  • Chris Marshall

    Chris Marshall - 2010-08-01

    Raising the priority for this request as it would be nice to finish for PDL-2.4.7

  • Chris Marshall

    Chris Marshall - 2010-08-01
    • priority: 1 --> 5
  • Chris Marshall

    Chris Marshall - 2010-08-01
    • assigned_to: nobody --> marshallch
  • Chris Marshall

    Chris Marshall - 2010-08-05

    I've implemented a simple check with prompt for
    previously existing PDL installs in @INC. That should
    help to alert users that a potential issue is there.

  • Chris Marshall

    Chris Marshall - 2010-08-05
    • status: open --> pending
  • SourceForge Robot

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

  • SourceForge Robot

    • status: pending --> closed

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks