Although it should theoretically be possible to build an entirely static Perl, it might involve an unnecessary amount of tweaking (in particular, if you also want libc to be linked in statically...). It's probably easier to just upload any required shared libs (see ldd output) together with the perl binary, and then have the environment variable LD_LIBRARY_PATH point to the directory where you're keeping those private libs... (preferably just for the CGI environment, so you don't risk messing up other things - see the apache docs for how to do that).
Update: As to the libc issue I hinted at above, I just remembered I wrote up something in a different forum some time ago. The context is a rather different one (so it's not a recipe on how to link Perl statically), but if you look for the -nodefaultlibs stuff, you'll get an idea of what things you'd have to mess with to get a truly static binary... - Just in case anyone is interested.
In reply to Re: real static perl
by almut
in thread real static perl
by bobb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |