While converter filled you in on the basics of the warning, there is no need to mess around with pod, although some would disagree, you can simply modify Makefile.PL. what h2xs -AX initially spits out is something like: 
use ExtUtils::MakeMaker;
# See lib/ExtUtils/MakeMaker.pm for details of how to influence
# the contents of the Makefile that is written.
WriteMakefile(
    'NAME'        => 'Foo::Bar::Baz',
    'VERSION_FROM'    => 'Baz.pm', # finds $VERSION
    'PREREQ_PM'        => {}, # e.g., Module::Name => 1.1
    ($] >= 5.005 ?    ## Add these new keywords supported since 5.005
      (ABSTRACT_FROM => 'Baz.pm', # retrieve abstract from module
       AUTHOR     => 'A. U. Thor <a.u.thor@a.galaxy.far.far.away>') : 
+()),
);

[download]
Just remove the ABSTRACT_FROM line, or cut off the _FROM part, and let 'Baz.pm' be the abstract.

You definetly ought to give the ExtUtils::MakeMaker pod a look see, as well as take a closer look at Makefile.PL and the actual makefile that gets generated. I had lots of fun reading those when I was writing Pod::Stripper, or should I say, when I was writing the Pod::Stripper "distribution". Concidentally, the Pod::Stripper abstract is (in pod form): 

=head1 NAME

Pod::Stripper - strip all pod, and output what's left

[download]
It's just a convention that most folk use Mod::Name - abstract here ... but since of the advent of ABSTRACT_FROM, I doubt anyone will change (I plan on staying lazy on that part).

Ok, enough shameless plugs. On a final note, I, and him, bot suggest you give perlmod and perlmodlib a few reads whilst devouring all the Make(file|Maker) stuff.

 
______crazyinsomniac_____________________________
Of all the things I've lost, I miss my mind the most.
perl -e "$q=$_;map({chr unpack qq;H*;,$_}split(q;;,q*H*));print;$q/$q;"

In reply to (crazyinsomniac) Re: What does this ABSTRACT warning from MakeMaker mean? by crazyinsomniac
in thread What does this ABSTRACT warning from MakeMaker mean? by ehdonhon

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.