There's more than one way to do things | |
PerlMonks |
Building perl in chrootby moot (Chaplain) |
on May 05, 2005 at 17:51 UTC ( [id://454447]=perlquestion: print w/replies, xml ) | Need Help?? |
moot has asked for the wisdom of the Perl Monks concerning the following question:
Hello Monks. Well I was hoping to complete this task without bothering SoPW, but both google and super-search have not been my friends. I'm building a newer version of perl (5.8.6) on a platform which is no longer supported and therefore has no package later than 5.6.1. It's being built on a system where I can't overwrite the existing perl (for various reasons) and will be deployed as a package to identical systems that lack for a compiler. Sounds like a job for chroot, I thought - build new perl, install it in a chroot environment, and then package up from there. However, the gods are not smiling. I receive the following error: ..this indicates to me that something is missing from the chroot environment (the same command launched from the same directory but without chrootiness works fine), but what? Attempts to run miniperl -Ilib -e with other code meets the 'Can't open perl script "-e"' error, but miniperl functions just fine as a stand-alone perl, i.e. when run without -e. Any ideas what could be missing? Has anymonk ever successfully installed perl in a chroot environment?
Back to
Seekers of Perl Wisdom
|
|