Re: Original name of a PAR-Packed shared object file?

Hi,

boot_IO means the original filename was IO.so on linux. On windows it would be IO.dll...

I cant remember, but maybe setting https://metacpan.org/pod/PAR%3A%3AEnvironment#PAR_GLOBAL_DEBUG mentions the original filename

What command did you use for packing?

Comment on Re: Original name of a PAR-Packed shared object file?

Replies are listed 'Best First'.
Re^2: Original name of a PAR-Packed shared object file? by ek15 (Novice) on Feb 21, 2018 at 18:38 UTC
I was able to verify that b1934410.so is in fact perl5/auto/IO/IO.so. Now I'm wondering why it would succeed on the build system, but fail on another system. The pp command is below. `pp -c -F Crypto -f Crypto -M Filter::Crypto::Decrypt -l /lib64/libcrypto.so.6 [various libs included] -o bin/switchscan switchscan.pl [various modules included]`	[reply] [d/l]
Re^3: Original name of a PAR-Packed shared object file? by beech (Parson) on Feb 23, 2018 at 22:24 UTC
Hi, Does adding `-x` switch change anything?	[reply] [d/l]
Re^4: Original name of a PAR-Packed shared object file? by ek15 (Novice) on Mar 02, 2018 at 17:48 UTC
Tried adding in the -x switch, no difference.	[reply]
Re^3: Original name of a PAR-Packed shared object file? by beech (Parson) on Feb 22, 2018 at 22:08 UTC
Hi What happens if you don't use filters?	[reply]
Re^4: Original name of a PAR-Packed shared object file? by ek15 (Novice) on Feb 23, 2018 at 17:42 UTC
Just tried this, removing `-F Crypto -f Crypto -M Filter::Crypto::Decrypt -l /lib64/libcrypto.so.6` from the pp command. I still get the above error.	[reply] [d/l]
Re^2: Original name of a PAR-Packed shared object file? by ek15 (Novice) on Feb 21, 2018 at 18:46 UTC
The same OS is installed on each system (Centos 7.2).	[reply]