PATH=C:\cpanfly-5.24-32\var\megalib\bin;C:\Perl-5.24-32\site\bin;C:\Perl-5.24-32\bin;C:\MinGW-32\bin;C:\cygwin\bin;C:\instantclient_11_2-32;C:\cpanfly-5.24-32\var\megalib\bin;C:\Perl-5.24-32\site\bin;C:\Perl-5.24-32\bin;C:\MinGW-32\bin;C:\cygwin\bin;C:\instantclient_11_2-32;C:\p4;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Git\cmd;C:\Program Files (x86)\CMake\bin Start 2016-07-23T13:10:43 ActivePerl-2400 CPAN-2.10 PATH=C:/CPANFL~2.24-/var/libs/bin;C:\CPANFL~2.24-\var\megalib\bin;C:\PERL-5~2.24-\site\bin;C:\PERL-5~2.24-\bin;C:\MinGW-32\bin;C:\cygwin\bin;C:\INSTAN~3;C:\CPANFL~2.24-\var\megalib\bin;C:\PERL-5~2.24-\site\bin;C:\PERL-5~2.24-\bin;C:\MinGW-32\bin;C:\cygwin\bin;C:\INSTAN~3;C:\p4;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WINDOW~1\v1.0\;C:\PROGRA~1\Git\cmd;C:\PROGRA~2\CMake\bin Reading 'C:\cpanfly-5.24-32\var\cpan\Metadata' Database was generated on Sat, 23 Jul 2016 02:41:02 GMT Checksum for C:\cpanfly-5.24-32\var\cpan\sources\authors\id\T\TI\TIMB\Apache-Status-DBI-1.012.tar.gz ok Apache-Status-DBI-1.012/ Apache-Status-DBI-1.012/Changes Apache-Status-DBI-1.012/lib/ Apache-Status-DBI-1.012/lib/Apache/ Apache-Status-DBI-1.012/lib/Apache/Status/ Apache-Status-DBI-1.012/lib/Apache/Status/DBI.pm Apache-Status-DBI-1.012/Makefile.PL Apache-Status-DBI-1.012/MANIFEST Apache-Status-DBI-1.012/META.yml Apache-Status-DBI-1.012/README Apache-Status-DBI-1.012/t/ Apache-Status-DBI-1.012/t/00.load.t Apache-Status-DBI-1.012/t/perlcritic.t Apache-Status-DBI-1.012/t/pod-coverage.t Apache-Status-DBI-1.012/t/pod.t Configuring T/TI/TIMB/Apache-Status-DBI-1.012.tar.gz with Makefile.PL >>> C:\Perl-5.24-32\bin\perl.exe Makefile.PL Checking if your kit is complete... Looks good Have \cpanfl~2.24-\var\megalib Want \perl-5~2.24-\lib Your perl and your Config.pm seem to have different ideas about the architecture they are running on. Perl thinks: [megalib] Config says: [MSWin32-x86-multi-thread-64int] This may or may not cause problems. Please check your installation of perl if you have problems building this extension. Generating a dmake-style Makefile Writing Makefile for Apache::Status::DBI Writing MYMETA.yml and MYMETA.json TIMB/Apache-Status-DBI-1.012.tar.gz C:\Perl-5.24-32\bin\perl.exe Makefile.PL -- OK Running make for T/TI/TIMB/Apache-Status-DBI-1.012.tar.gz >>> dmake cp lib/Apache/Status/DBI.pm blib\lib\Apache\Status\DBI.pm TIMB/Apache-Status-DBI-1.012.tar.gz dmake -- OK Running make test >>> dmake test TEST_VERBOSE=1 "C:\Perl-5.24-32\bin\perl.exe" "-MExtUtils::Command::MM" "-MTest::Harness" "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib\lib', 'blib\arch')" t/*.t # Failed test 'use Apache::Status::DBI;' # at t/00.load.t line 4. # Tried to use 'Apache::Status::DBI'. # Error: Can't locate Apache.pm in @INC (you may need to install the Apache module) (@INC contains: C:\cpanfly-5.24-32\var\tmp\cpan_build\Apache-Status-DBI-1.012-Ty9yZA\blib\lib C:\cpanfly-5.24-32\var\tmp\cpan_build\Apache-Status-DBI-1.012-Ty9yZA\blib\arch C:/cpanfly-5.24-32/var/megalib C:/cpanfly-5.24-32/var/megalib C:/Perl-5.24-32/site/lib C:/Perl-5.24-32/lib .) at C:\cpanfly-5.24-32\var\tmp\cpan_build\Apache-Status-DBI-1.012-Ty9yZA\blib\lib/Apache/Status/DBI.pm line 30. # BEGIN failed--compilation aborted at C:\cpanfly-5.24-32\var\tmp\cpan_build\Apache-Status-DBI-1.012-Ty9yZA\blib\lib/Apache/Status/DBI.pm line 34. # Compilation failed in require at t/00.load.t line 4. # BEGIN failed--compilation aborted at t/00.load.t line 4. # Testing Apache::Status::DBI # Looks like you failed 1 test of 1. t/00.load.t ....... 1..1 not ok 1 - use Apache::Status::DBI; Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests # Failed test 'Test::Perl::Critic for "blib\lib\Apache\Status\DBI.pm"' # at C:/cpanfly-5.24-32/var/megalib/Test/Perl/Critic.pm line 104. # # Use of "require" is not allowed at line 15, column 18. Use Require() method of MainObject instead. (Severity: 5) # Use of "require" is not allowed at line 19, column 9. Use Require() method of MainObject instead. (Severity: 5) # Use of "require" is not allowed at line 20, column 9. Use Require() method of MainObject instead. (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 21, column 9. (no explanation). (Severity: 5) # Use of "require" is not allowed at line 30, column 9. Use Require() method of MainObject instead. (Severity: 5) # Use of "require" is not allowed at line 31, column 9. Use Require() method of MainObject instead. (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 36, column 4. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 39, column 4. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 41, column 5. (no explanation). (Severity: 5) # Use of low precedence operators is not allowed at line 44, column 8. Replace low precedence operators with the high precedence substitutes. (Severity: 5) # Use of low precedence operators is not allowed at line 45, column 8. Replace low precedence operators with the high precedence substitutes. (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 46, column 8. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 48, column 5. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 49, column 17. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 49, column 23. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 49, column 42. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 50, column 9. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 50, column 41. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 50, column 50. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 67, column 1. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 73, column 8. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 74, column 62. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 74, column 88. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 76, column 17. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 76, column 37. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 78, column 12. (no explanation). (Severity: 5) # Private Member Data shouldn't be accessed directly at line 78, column 43. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 81, column 20. (no explanation). (Severity: 5) # Private Member Data shouldn't be accessed directly at line 81, column 45. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5) # Private Member Data shouldn't be accessed directly at line 81, column 68. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 83, column 9. (no explanation). (Severity: 5) # Private Member Data shouldn't be accessed directly at line 83, column 29. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5) # Private Member Data shouldn't be accessed directly at line 83, column 52. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 83, column 72. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 84, column 55. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 95, column 1. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 96, column 13. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 97, column 8. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 97, column 24. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 98, column 8. (no explanation). (Severity: 5) # Private Member Data shouldn't be accessed directly at line 98, column 16. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 99, column 8. (no explanation). (Severity: 5) # Private Member Data shouldn't be accessed directly at line 99, column 39. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 100, column 8. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 104, column 8. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 107, column 8. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 110, column 9. (no explanation). (Severity: 5) # Private Member Data shouldn't be accessed directly at line 111, column 85. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 112, column 9. (no explanation). (Severity: 5) # Private Member Data shouldn't be accessed directly at line 112, column 29. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5) # Private Member Data shouldn't be accessed directly at line 112, column 57. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 112, column 82. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 113, column 14. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 114, column 14. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 118, column 14. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 121, column 44. (no explanation). (Severity: 5) # Private Member Data shouldn't be accessed directly at line 122, column 27. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 122, column 38. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 123, column 44. (no explanation). (Severity: 5) # Private Member Data shouldn't be accessed directly at line 124, column 42. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 124, column 54. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 125, column 12. (no explanation). (Severity: 5) # Private Member Data shouldn't be accessed directly at line 125, column 31. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 126, column 9. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 127, column 54. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 127, column 60. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 128, column 27. (no explanation). (Severity: 5) # Private Member Data shouldn't be accessed directly at line 128, column 44. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 129, column 49. (no explanation). (Severity: 5) # Private Member Data shouldn't be accessed directly at line 130, column 50. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 133, column 44. (no explanation). (Severity: 5) # Private Member Data shouldn't be accessed directly at line 134, column 42. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 134, column 54. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 135, column 12. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 136, column 38. (no explanation). (Severity: 5) # Method invocation should use "()" at line 136, column 46. Use "->MethodName()" instead of "->MethodName". (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 137, column 12. (no explanation). (Severity: 5) # Method invocation should use "()" at line 137, column 31. Use "->MethodName()" instead of "->MethodName". (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 138, column 21. (no explanation). (Severity: 5) # Method invocation should use "()" at line 138, column 30. Use "->MethodName()" instead of "->MethodName". (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 139, column 42. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 140, column 14. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 140, column 38. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 141, column 13. (no explanation). (Severity: 5) # Method invocation should use "()" at line 141, column 33. Use "->MethodName()" instead of "->MethodName". (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 144, column 16. (no explanation). (Severity: 5) # Private Member Data shouldn't be accessed directly at line 144, column 41. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5) # Private Member Data shouldn't be accessed directly at line 144, column 64. Accessing an objects data directly breaks encapsulation and should be avoided. Example: $object->{ some_key }. (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 145, column 12. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 148, column 50. (no explanation). (Severity: 5) # Variable, subroutine, and package names have to be in CamelCase at line 148, column 64. (no explanation). (Severity: 5) t/perlcritic.t .... not ok - Test::Perl::Critic for "blib\lib\Apache\Status\DBI.pm" 1..1 Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests # Failed test 'Pod coverage on Apache::Status::DBI' # at C:/cpanfly-5.24-32/var/megalib/Test/Pod/Coverage.pm line 133. # Apache::Status::DBI: requiring 'Apache::Status::DBI' failed # Looks like you failed 1 test of 1. t/pod-coverage.t .. 1..1 not ok 1 - Pod coverage on Apache::Status::DBI Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests t/pod.t ........... 1..1 ok 1 - POD test for blib/lib/Apache/Status/DBI.pm ok Test Summary Report ------------------- t/00.load.t (Wstat: 256 Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 1 t/perlcritic.t (Wstat: 256 Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 1 t/pod-coverage.t (Wstat: 256 Tests: 1 Failed: 1) Failed test: 1 Non-zero exit status: 1 Files=4, Tests=4, 5 wallclock secs ( 0.05 usr + 0.01 sys = 0.06 CPU) Result: FAIL Failed 3/4 test programs. 3/4 subtests failed. dmake: Error code 255, while making 'test_dynamic' TIMB/Apache-Status-DBI-1.012.tar.gz dmake test TEST_VERBOSE=1 -- NOT OK //hint// to see the cpan-testers results for installing this module, try: reports TIMB/Apache-Status-DBI-1.012.tar.gz Finished 2016-07-23T13:11:00