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.

Hey, thanks, those are good tips.

I solved my problem, see the O.P.

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