Checking if your kit is complete... Looks good Writing Makefile for Email::AddressParser cp lib/Email/AddressParser.pm blib/lib/Email/AddressParser.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 AddressParser.xs > AddressParser.xsc && mv AddressParser.xsc AddressParser.c Please specify prototyping behavior for AddressParser.xs (see perlxs manual) 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.04\" -DXS_VERSION=\"0.04\" +Z "-I/home/cpanrun/pa-risc1.1/build/5.8.2/lib/5.8.2/PA-RISC1.1-thread-multi/CORE" AddressParser.c Running Mkbootstrap for Email::AddressParser () chmod 644 AddressParser.bs rm -f blib/arch/auto/Email/AddressParser/AddressParser.sl LD_RUN_PATH="" /usr/bin/ld -b +vnocompatwarnings AddressParser.o -o blib/arch/auto/Email/AddressParser/AddressParser.sl chmod 755 blib/arch/auto/Email/AddressParser/AddressParser.sl cp AddressParser.bs blib/arch/auto/Email/AddressParser/AddressParser.bs chmod 644 blib/arch/auto/Email/AddressParser/AddressParser.bs Manifying blib/man3/Email::AddressParser.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/Email-AddressParser....1..8 ok 1 - use Email::AddressParser; ok 2 - object interface ok 3 - object interface make: *** [test_dynamic] Hangup