in reply to Re: Pelr packer pp with -C fails else ok
in thread Pelr packer pp with -C fails else ok
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"
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)
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^3: Pelr packer pp with -C fails else ok
by swl (Prior) on Oct 04, 2018 at 22:36 UTC | |
by dkhosla1 (Sexton) on Oct 06, 2018 at 00:17 UTC | |
by swl (Prior) on Oct 06, 2018 at 06:59 UTC | |
by dkhosla1 (Sexton) on Oct 06, 2018 at 13:50 UTC | |
by swl (Prior) on Oct 06, 2018 at 23:35 UTC | |
| |
by Anonymous Monk on Oct 06, 2018 at 00:42 UTC | |
by dkhosla1 (Sexton) on Oct 06, 2018 at 04:48 UTC | |
|
Re^3: Pelr packer pp with -C fails else ok
by dkhosla1 (Sexton) on Oct 06, 2018 at 00:10 UTC |