PATH=/usr/bin:/bin:/data/fly2400/cpanfly-5.24/var/megalib/bin Start 2017-01-06T04:01:55 ActivePerl-2400 CPAN-2.10 Reading '/data/fly2400/cpanfly-5.24/var/cpan/Metadata' Database was generated on Fri, 06 Jan 2017 05:53:30 GMT Fetching with LWP: http://ppm.activestate.com/CPAN/authors/id/I/IN/INGY/XXX-0.31.tar.gz Fetching with LWP: http://ppm.activestate.com/CPAN/authors/id/I/IN/INGY/CHECKSUMS Checksum for /data/fly2400/cpanfly-5.24/var/cpan/sources/authors/id/I/IN/INGY/XXX-0.31.tar.gz ok XXX-0.31 XXX-0.31/README XXX-0.31/Changes XXX-0.31/LICENSE XXX-0.31/t XXX-0.31/t/test.t XXX-0.31/MANIFEST XXX-0.31/META.yml XXX-0.31/t/regex.t XXX-0.31/META.json XXX-0.31/lib XXX-0.31/lib/XXX.pm XXX-0.31/lib/XXX.pod XXX-0.31/t/require.t XXX-0.31/Makefile.PL XXX-0.31/CONTRIBUTING XXX-0.31/t/author-pod-syntax.t XXX-0.31/t/000-compile-modules.t Configuring I/IN/INGY/XXX-0.31.tar.gz with Makefile.PL >>> /data/fly2400/ap2400-300558/bin/perl-static Makefile.PL Checking if your kit is complete... Looks good Have /data/fly2400/cpanfly-5.24/var/megalib Want /home/fly2400/ap2400-300558/lib Your perl and your Config.pm seem to have different ideas about the architecture they are running on. Perl thinks: [megalib] Config says: [x86_64-linux-thread-multi] This may or may not cause problems. Please check your installation of perl if you have problems building this extension. Generating a Unix-style Makefile Writing Makefile for XXX Writing MYMETA.yml and MYMETA.json INGY/XXX-0.31.tar.gz /data/fly2400/ap2400-300558/bin/perl-static Makefile.PL -- OK Running make for I/IN/INGY/XXX-0.31.tar.gz >>> make cp lib/XXX.pod blib/lib/XXX.pod cp lib/XXX.pm blib/lib/XXX.pm Manifying 1 pod document INGY/XXX-0.31.tar.gz make -- OK Running make test >>> make test TEST_VERBOSE=1 PERL_DL_NONLAZY=1 "/data/fly2400/ap2400-300558/bin/perl-static" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 'blib/arch')" t/*.t t/000-compile-modules.t .. ok 1 - use XXX; 1..1 ok t/author-pod-syntax.t .... skipped: these tests are for testing by the author t/regex.t ................ 1..4 ok 1 - has the string ok 2 - has the capture pattern ok 3 - has the string ok 4 - has the capture pattern ok t/require.t .............. 1..2 ok 1 - YAML Dump Worked for "require XXX" ok 2 - YAML Dump Worked with $DumpModule ok t/test.t ................. 1..1 ok 1 - Everything compiled ok All tests successful. Files=5, Tests=8, 0 wallclock secs ( 0.04 usr 0.00 sys + 0.34 cusr 0.07 csys = 0.45 CPU) Result: PASS INGY/XXX-0.31.tar.gz make test TEST_VERBOSE=1 -- OK Ingy dot Net <ingy@cpan.org> See Your Data in the Nude >>> (cd /data/fly2400/cpanfly-5.24/var/tmp/cpan_build/XXX-0.31-lUMs8C && tar cvf - XXX-0.31.ppd blib) | gzip -c >/data/fly2400/cpanfly-5.24/var/REPO/I/IN/INGY/XXX-0.31.tar.gz XXX-0.31.ppd blib/ blib/man3/ blib/man3/XXX.3 blib/lib/ blib/lib/XXX.pm blib/lib/XXX.pod VmSize: 356224 kB Finished 2017-01-06T04:02:00