in reply to Re^2: Module Install Troubles
in thread Module Install Troubles

Can you install any perl modules? If you can't install any, then your looking at a system setup problem. If you only can't install DBM::Deep, then you should concentrate on DBM::Deep itself.

The path to make at '/home/sgriffith/unix/bin/make' looks really odd. I'd expect it to try and use '/usr/bin/make'. Do you know why it's trying to use that copy of make? If it's not something you've done on purpose, then it's probably your problem.

--Pileofrogs

Replies are listed 'Best First'.
Re^4: Module Install Troubles
by QM (Parson) on Aug 21, 2008 at 20:06 UTC
    That path to make is my own install of GNU make. I've since switched back to the system supplied make, with no apparent difference.

    I've gone through and installed some of the dependencies separately through cpan, some install, some don't. The biggest headache seems to be Test::Exception:

    # BEGIN failed--compilation aborted at /otdp1_vol1/home/sgriffit/.cpan/build/Test-Exception-0.27/blib/lib/Test/Exception.pm line 6.
    # Compilation failed in require at (eval 2) line 2.
    # BEGIN failed--compilation aborted at (eval 2) line 2.

    # Failed test 'cannot pass undef to throws_ok'

    -QM
    --
    Quantum Mechanics: The dreams stuff is made of

[reply]

      Okay, if I reach a point like this, I usually start tinkering with the build by hand. You can go to the build dir in your cpan dir and find the source all unpacked for you. Then you can run make test with the verbosity turned up and that might help.

      $ make test TEST_VERBOSE=1

      [download]

      (I think that's the right syntax)

      Another good thing to try is (from the base dir of the unpacked module source)

      $ prove -v -I lib t/TESTNAME

      [download]

      Where TESTNAME is the name of one of the files in the t/ dir. This lets you test one test at a time, and it turns on the verbosity. Read the man page on prove, it's cool.

      And then poke around in the t/ directory and read the tests that are failing.

      Another thing that can cause problems that are hard to track down is when you install stuff as root with your umask too tight. In English, that means you install stuff and then your non-root account can't read it. If it's a perl dependency, you get the regular lib-not-found error, but if it's some non-perl dependency, you can get the kind of thing you're seeing.

[reply]
[d/l]
[select]
        Hey, thanks, those are good tips.

        I solved my problem, see the O.P.

        -QM
        --
        Quantum Mechanics: The dreams stuff is made of

[reply]

In Section Seekers of Perl Wisdom