You may need to wait until your CPAN mirror catches up. (Or switch to a mirror that updates more frequently.)

As for testing, as a start, just try to install it using CPAN -- i.e. run our tests. Better yet, install and configure CPAN::Reporter first. That way, if it fails, we'll get notified automatically via CPAN Testers.

Second, try it from the command line on some libraries on your system. Pick something you know you have and pick something you know you don't have.

E.g., for me, with Strawberry Perl (Win32):

C:\david\svk>perl -MDevel::CheckLib -e "assert_lib( lib => q{m} )"

C:\david\svk>perl -MDevel::CheckLib -e "assert_lib( lib => q{jpeg} )"
Can't build and link to 'jpeg'
[download]

Or, on linux:

$ perl -MDevel::CheckLib -e 'assert_lib( lib => "jpeg" )'

$ perl -MDevel::CheckLib -e 'assert_lib( lib => "m" )'    

$ perl -MDevel::CheckLib -e 'assert_lib( lib => "iconv" )'    
Can't build and link to 'iconv'
[download]

If it doesn't give you the results you expect for those libraries, let us know, along with your perl -V output.

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

Thanks - I am going to test it out on AIX (xlc). I'll get back with the results once I have something for you.

Also, I'm not sure if this is in the scope, but it would be great to have an option for a module to have a chance to re-run Makefile.PL after the missing dependencies were installed. Imagine one day someone releases something like bin::libjpeg.pm that installs libjpeg.so, and that can actually be used as an installable dependency.

The bit that goes at the start of Makefile.PL (or Build.PL) looks something like this:

use lib qw(inc);
use Devel::CheckLib;

# Prompt the user here for any paths and other configuration

check_lib_or_exit(
    # fill in what you prompted the user for here
    lib => [qw(cthulhu fhtagn)]
);
[download]

While you could, in theory, extract all the relevant code from the module and put it straight into your Makefile.PL, there's a *lot* of it. Building and linking C code in a cross-platform way is a pain in the arse.