I think the absence of the par-xxx path(s) in @INC is a key symptom. Does your code modify @INC in any way?

What happens if you build an executable that only prints @INC? Like this (adjusting quote chars as needed for linux): 

pp -C -e "print join q{ }, @INC"

[download]

If I run it on my windows machine using PAR::Packer 1.047, I get the result below. Note the absence of any of the lib dirs from the perl it was built with.

a.exe
C:\Users\user\AppData\Local\Temp\par-736861776e\temp-21884\inc\lib C:\
+Users\user\AppData\Local\Temp\par-736861776e\temp-21884\inc CODE(0x38
+59d88) CODE(0x385a310)

[download]

In reply to Re^2: Pelr packer pp with -C fails else ok by swl
in thread Pelr packer pp with -C fails else ok by dkhosla1

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.