I've had issues with diagnostics on machines that aren't set up perfectly - and that's without PAR. For example, installing ActiveState Perl for Windows to a network share, and then everyone copying the shared version locally (for performance reasons). (Not my design.)

What happens is that the diagnostics module will look in Config for where Perl is installed, and then look for perldiag.pod there. And that's where your trouble is. If only perldiag.pod were in the __END__ section of diagnostics.pm, PAR probably would incorporate it properly.

I know this isn't a solution - short of "don't use that module in a PAR-enabled app", I don't have one. Mostly because I don't use PAR. But perhaps that will help you track down a solution.


In reply to Re: diagnostics pragma and PAR/pp by Tanktalus
in thread diagnostics pragma and PAR/pp by rvosa

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.