I don't think you are doing it right. I mean, the idea is good, but the execution is poorly. Sure, you have eliminated the include path. But what about the path to perl? Why depend on perl being installed? What if the installed perl was configured with the "wrong" options? What about missing system libraries, or wrong versions of them, or strangely set LD_LIBRARY_PATHs? Why depend on that?

No, the least thing you should do is write a C program, include a Perl interpreter from the C program, and run your Perl code from within that interpreter. And then when you compile, statically link everything in. Only then you have a reasonable chance someone else will be able to run it. And it's really neat for the maintenance programmer.

But it might even be better if you put this program on a bootable CD-ROM, so you will sure it's going to be run in the right OS.

Code reuse is for wussies.

Abigail