Checking if your kit is complete... Looks good Writing Makefile for BSD::getloadavg cp lib/BSD/getloadavg.pm blib/lib/BSD/getloadavg.pm /home/cpanrun/pa-risc1.1/build/5.8.2/bin/perl /home/cpanrun/pa-risc1.1/build/5.8.2/lib/5.8.2/ExtUtils/xsubpp -typemap /home/cpanrun/pa-risc1.1/build/5.8.2/lib/5.8.2/ExtUtils/typemap getloadavg.xs > getloadavg.xsc && mv getloadavg.xsc getloadavg.c cc -c -I. -D_POSIX_C_SOURCE=199506L -D_REENTRANT -Ae -D_HPUX_SOURCE -Wl,+vnocompatwarnings -DNO_HASH_SEED -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fast +Onolimit +Opromote_indirect_calls +DAportable +DS2.0 -DVERSION=\"0.03\" -DXS_VERSION=\"0.03\" +Z "-I/home/cpanrun/pa-risc1.1/build/5.8.2/lib/5.8.2/PA-RISC1.1-thread-multi/CORE" getloadavg.c Running Mkbootstrap for BSD::getloadavg () chmod 644 getloadavg.bs rm -f blib/arch/auto/BSD/getloadavg/getloadavg.sl LD_RUN_PATH="" /usr/bin/ld -b +vnocompatwarnings getloadavg.o -o blib/arch/auto/BSD/getloadavg/getloadavg.sl chmod 755 blib/arch/auto/BSD/getloadavg/getloadavg.sl cp getloadavg.bs blib/arch/auto/BSD/getloadavg/getloadavg.bs chmod 644 blib/arch/auto/BSD/getloadavg/getloadavg.bs Manifying blib/man3/BSD::getloadavg.3 PERL_DL_NONLAZY=1 /home/cpanrun/pa-risc1.1/build/5.8.2/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(1, 'blib/lib', 'blib/arch')" t/*.t t/BSD-getloadavg....1..5 /usr/lib/dld.sl: Unresolved symbol: getloadavg (code) from /home/cpanrun/depot/main/contrib-patched/perl/CPAN/src/BSD-getloadavg/blib/arch/auto/BSD/getloadavg/getloadavg.sl # Failed test (t/BSD-getloadavg.t at line 9) # Tried to use 'BSD::getloadavg'. # Error: Can't load '/home/cpanrun/depot/main/contrib-patched/perl/CPAN/src/BSD-getloadavg/blib/arch/auto/BSD/getloadavg/getloadavg.sl' for module BSD::getloadavg: Unresolved external at /home/cpanrun/pa-risc1.1/build/5.8.2/lib/5.8.2/PA-RISC1.1-thread-multi/DynaLoader.pm line 229. # at (eval 1) line 2 # Compilation failed in require at (eval 1) line 2. Undefined subroutine &main::getloadavg called at t/BSD-getloadavg.t line 10. not ok 1 - use BSD::getloadavg; # Looks like you planned 5 tests but only ran 1. # Looks like your test died just after 1. dubious Test returned status 255 (wstat 65280, 0xff00) DIED. FAILED tests 1-5 Failed 5/5 tests, 0.00% okay Failed 1/1 test scripts, 0.00% okay. 5/5 subtests failed, 0.00% okay. Failed Test Stat Wstat Total Fail Failed List of Failed --------------------------------------------------------------------------------------------------------------------------- t/BSD-getloadavg.t 255 65280 5 9 180.00% 1-5 make: *** [test_dynamic] Error 2