Checking if your kit is complete...
Looks good
Writing Makefile for DBIx::Browse::CGI
Writing Makefile for DBIx::Browse
cp Browse.pm blib/lib/DBIx/Browse.pm
cp CGI.pm ../blib/lib/DBIx/Browse/CGI.pm
Manifying ../blib/man3/DBIx::Browse::CGI.3
Manifying blib/man3/DBIx::Browse.3
PERL_DL_NONLAZY=1 /Users/cpanrun/build/5.10.0/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(1, 'blib/lib', 'blib/arch')" t/*.t
t/01-use....1..4
ok 1 - use CGI;
ok 2 - use DBI;
ok 3 - use DBIx::Browse;
Ambiguous call resolved as CORE::die(), qualify as such or use & at
	/Users/cpanrun/build/5.10.0/site/lib/CGI/Carp.pm line 221 (#1)
    (W ambiguous) A subroutine you have declared has the same name as a Perl
    keyword, and you have used the name without qualification for calling
    one or the other.  Perl decided to call the builtin because the
    subroutine is not imported.
    
    To force interpretation as a subroutine call, either put an ampersand
    before the subroutine name, or qualify the name with its package.
    Alternatively, you can import the subroutine (or pretend that it's
    imported with the use subs pragma).
    
    To silently interpret it as the Perl operator, use the CORE:: prefix
    on the operator (e.g. CORE::log($x)) or declare the subroutine
    to be an object method (see perlsub/"Subroutine Attributes" or
    attributes).
    
ok 4 - use DBIx::Browse::CGI;
ok
t/02-db.....1..17
Ambiguous call resolved as CORE::die(), qualify as such or use & at
	/Users/cpanrun/build/5.10.0/site/lib/CGI/Carp.pm line 221 (#1)
    (W ambiguous) A subroutine you have declared has the same name as a Perl
    keyword, and you have used the name without qualification for calling
    one or the other.  Perl decided to call the builtin because the
    subroutine is not imported.
    
    To force interpretation as a subroutine call, either put an ampersand
    before the subroutine name, or qualify the name with its package.
    Alternatively, you can import the subroutine (or pretend that it's
    imported with the use subs pragma).
    
    To silently interpret it as the Perl operator, use the CORE:: prefix
    on the operator (e.g. CORE::log($x)) or declare the subroutine
    to be an object method (see perlsub/"Subroutine Attributes" or
    attributes).
    
ok 1 # skip database tests (see README file on how to allow them)
ok 2 # skip database tests (see README file on how to allow them)
ok 3 # skip database tests (see README file on how to allow them)
ok 4 # skip database tests (see README file on how to allow them)
ok 5 # skip database tests (see README file on how to allow them)
ok 6 # skip database tests (see README file on how to allow them)
ok 7 # skip database tests (see README file on how to allow them)
ok 8 # skip database tests (see README file on how to allow them)
ok 9 # skip database tests (see README file on how to allow them)
ok 10 # skip database tests (see README file on how to allow them)
ok 11 # skip database tests (see README file on how to allow them)
ok 12 # skip database tests (see README file on how to allow them)
ok 13 # skip database tests (see README file on how to allow them)
ok 14 # skip database tests (see README file on how to allow them)
ok 15 # skip database tests (see README file on how to allow them)
ok 16 # skip database tests (see README file on how to allow them)
ok 17 # skip database tests (see README file on how to allow them)
ok
        17/17 skipped: various reasons
All tests successful, 17 subtests skipped.
Files=2, Tests=21,  1 wallclock secs ( 0.73 cusr +  0.15 csys =  0.88 CPU)
No tests defined for DBIx::Browse::CGI extension.
make: *** [htmlifypods] Hangup