Huh? So you're double clicking on Makefile.PL? Don't do that.

I gotta say by the looks of Exporter-VA-1.2.2, I'd never consider testing it, much less installing it.

First, your program is pure perl, and it should follow the standard way for installing perl modules, which is not double click, which is not ./Makefile.PL, it is perl Makefile.PL, make, make test, make install.

Here's how you should think about changing it (dir structure first). 

E:\NEW\EXPORTER-VA-1.2.2
|   Exporter-VA-Convert.perl
|   Makefile.PL
|   MANIFEST.txt
|   README.txt
|   VA.pm
|
\---t
        00-basic.t
        M1.pm
        M2.pm
        M3.pm
I moved all the M*.pm files to the 't' directory, and I renamed test1.perl to 00-basic.t (which i also moved to 't'), and prepended use lib 't'; to it.

I also renamed Exporter-VA.pm to VA.pm. Everything went fine, except your test file, well, ins't a perl test file (you don't have a 1..numberOfTests line). You should read this perl.com article on testing.

The simple way of testing, is to have a single test.pl in the same directory as the Makefile.PL, like so 

E:\NEW\EXPORTER-VA-1.2.2
|   Exporter-VA-Convert.perl
|   Makefile.PL
|   MANIFEST.txt
|   README.txt
|   test.pl
|   VA.pm
|
\---t
        M1.pm
        M2.pm
        M3.pm

Here's the Makefile.PL 

use ExtUtils::MakeMaker;
# See lib/ExtUtils/MakeMaker.pm for details of how to influence
# the contents of the Makefile that is written.
WriteMakefile(
    'NAME'        => 'Exporter::VA',
    'VERSION_FROM'    => 'VA.pm', # finds $VERSION
    'EXE_FILES'     => [qw[ Exporter-VA-Convert.perl ]],
    'PREREQ_PM'        => {}, # e.g., Module::Name => 1.1
    ($] >= 5.005 ?    ## Add these new keywords supported since 5.005
      (ABSTRACT_FROM => 'VA.pm', # retrieve abstract from module
       AUTHOR     => 'A. U. Thor <a.u.thor@a.galaxy.far.far.away>') : 
+()),
);

[download]
This is what `h2xs -AX -n Exporter::VA' basically gives you. 
Writing Exporter/VA/VA.pm
Writing Exporter/VA/Makefile.PL
Writing Exporter/VA/README
Writing Exporter/VA/test.pl
Writing Exporter/VA/Changes
Writing Exporter/VA/MANIFEST
Notice where VA.pm is? If it was Exporter-VA.pm, MakeMaker would not magically rename it to Exporter\VA.pm

MJD says you can't just make shit up and expect the computer to know what you mean, retardo!
** The Third rule of perl club is a statement of fact: pod is sexy.

In reply to Re: Makefile.PL even weirder on Windows by PodMaster
in thread Makefile.PL even weirder on Windows by John M. Dlugosz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.