[ info] generating script t/TEST Checking if your kit is complete... Looks good Writing Makefile for ModPerl::PackageRegistry cp lib/ModPerl/PackageRegistry.pm blib/lib/ModPerl/PackageRegistry.pm Manifying blib/man3/ModPerl::PackageRegistry.3 /home/cpanrun/pa-risc1.1/build/5.8.2/bin/perl -Iblib/arch -Iblib/lib \ t/TEST -clean [warning] setting ulimit to allow core files ulimit -c unlimited; /home/cpanrun/pa-risc1.1/build/5.8.2/bin/perl /home/cpanrun/depot/main/contrib-patched/perl/CPAN/src/ModPerl-PackageRegistry/t/TEST -clean APACHE_TEST_GROUP= APACHE_TEST_HTTPD= APACHE_TEST_PORT= APACHE_TEST_USER= APACHE_TEST_APXS= \ /home/cpanrun/pa-risc1.1/build/5.8.2/bin/perl -Iblib/arch -Iblib/lib \ t/TEST -bugreport -verbose=1 [warning] setting ulimit to allow core files ulimit -c unlimited; /home/cpanrun/pa-risc1.1/build/5.8.2/bin/perl /home/cpanrun/depot/main/contrib-patched/perl/CPAN/src/ModPerl-PackageRegistry/t/TEST -bugreport -verbose=1 [ error] STDIN is not attached to tty, skip interactive config [ error] Skipping the test suite execution, while returning success status Running the test suite is important to make sure that the module that you are about to install works on your system. If you choose not to run the test suite and you have a problem using this module, make sure to return and run this test suite before reporting any problems to the developers of this module. Installing /home/cpanrun/pa-risc1.1/build/5.8.2/lib/site_perl/5.8.2/ModPerl/PackageRegistry.pm Installing /home/cpanrun/pa-risc1.1/build/5.8.2/man/man3/ModPerl::PackageRegistry.3 Appending installation info to /home/cpanrun/pa-risc1.1/build/5.8.2/lib/5.8.2/PA-RISC1.1-thread-multi/perllocal.pod