in reply to Re^2: Problem while installing module from CPAN on windows.
in thread Problem while installing module from CPAN on windows.

You seem to be ignoring advice, but I'll try again. The build.log tells you where the problems are. You don't have to keep uploading broken module after broken module to cpan to test this out, simply trying to install your own module from the command line will also fail. Please consider renaming your module. IMHO modules should only be released to cpan when they are ready, this one has many mistakes. Previously I've emailed you at your cpan address to make you aware of these issues. Please read and understand the replies you already have.

Update your email just bounced:

The error that the other server returned was: 554 5.7.1 <removed@cpan.org>: Recipient address rejected: Access denie +d

Replies are listed 'Best First'.
Re^4: Problem while installing module from CPAN on windows.
by kiranp (Novice) on Sep 02, 2014 at 14:58 UTC

    Marto sorry i know i did many mistakes

    can u Please tell me how to install module from this distibution on windows

    my module need Benchmark.pm to as pre-requisites

    What problem do you think with this name *Speedometer*

    ,

    Can you please tell me. thanks.

      "can u Please tell me how to install module from this distibution on windows"

      Once you have built your distribution, change into the directory and type:

      cpanm .

      For exmple:

      D:\Speedometer-1.06>cpanm . --> Working on . Configuring D:/Speedometer-1.06 ... OK Building and testing Speedometer-1.06 ... FAIL ! Installing . failed. See D:\perl\data\.cpanm\work\1409669980.2756\bu +ild.log for details. Retry with --force to force install it.

      Then you can view the build log.

      "What problem do you think with this name *Speedometer*"

      Have you seen how cpan is structured? Did you read the link I gave you earler? Read on.

Re^4: Problem while installing module from CPAN on windows.
by kiranp (Novice) on Sep 02, 2014 at 15:15 UTC

    Thanks.

    How about Code::Speedometer name.

    also please tell me why there was problem in distribution

      The current issue is caused by the time the Makefile.PL has:

      Directory of D:\Speedometer-1.06 02/09/2014 16:51 <DIR> . 02/09/2014 16:51 <DIR> .. 02/09/2014 19:27 116 Changes 02/09/2014 19:27 210 ignore.txt 02/09/2014 15:37 <DIR> lib 02/09/2014 16:51 28,264 Makefile 02/09/2014 19:51 761 Makefile.PL 02/09/2014 19:27 135 MANIFEST 02/09/2014 16:51 1,011 MYMETA.json 02/09/2014 16:51 602 MYMETA.yml 02/09/2014 19:41 2,822 README 02/09/2014 15:37 <DIR> t 8 File(s) 33,921 bytes 4 Dir(s) 94,930,903,040 bytes free

      19:51 when here it's currently 16:53. Remove a blank line, saved it and:

      D:\Speedometer-1.06>perl Makefile.PL Generating a dmake-style Makefile Writing Makefile for Speedometer Writing MYMETA.yml and MYMETA.json D:\Speedometer-1.06>dmake cp lib/Speedometer.pm blib\lib\Speedometer.pm D:\Speedometer-1.06>dmake test D:\perl\perl\bin\perl.exe "-MExtUtils::Command::MM" "-MTest::Harness" +"-e" "undef *Test::Harness::Switches; test_harness(0, 'blib\lib', 'bl +ib\arch')" t/*.t t/00-load.t ....... # Testing Speedometer 1.06, Perl 5.020000, D:\perl +\perl\bin\perl.exe t/00-load.t ....... ok t/boilerplate.t ... ok t/manifest.t ...... Malformed UTF-8 character (unexpected end of strin +g) in substitution iterator at D:/perl/perl/vendor/lib/Portable/Confi +g.pm line 46. t/manifest.t ...... skipped: Author tests not required for installatio +n t/pod-coverage.t .. skipped: Test::Pod::Coverage 1.08 required for tes +ting POD coverage t/pod.t ........... skipped: Test::Pod 1.22 required for testing POD All tests successful. Test Summary Report ------------------- t/boilerplate.t (Wstat: 0 Tests: 3 Failed: 0) TODO passed: 1 Files=5, Tests=4, 1 wallclock secs ( 0.05 usr + 0.01 sys = 0.06 CPU +) Result: PASS D:\Speedometer-1.06>dmake install Installing D:\perl\perl\site\lib\Speedometer.pm Appending installation info to D:\perl\perl\lib/perllocal.pod

      I think you should do some research on this, tye (click search on that page) has some insight into the use and abuse of Benchmark.pm, and other benchmarking techniques which is worthwhile reading.

      Code::Speedometer isn't much better because it doesn't say anything about what the module actually does, and the Code:: namespace doesn't seem appropriate.

      For advice on naming, please see: PAUSE: On The Naming of Modules and perlmodstyle. You can also ask for advice on perl.module-authors, perl.modules, and http://prepan.org/

      Since your module claims to be "An easy interface to the Benchmark module", something in the Benchmark:: namespace might be appropriate.