… | |
… | |
122 | often as necessary. |
122 | often as necessary. |
123 | |
123 | |
124 | =head1 THE F<STATICPERL> SCRIPT |
124 | =head1 THE F<STATICPERL> SCRIPT |
125 | |
125 | |
126 | This module installs a script called F<staticperl> into your perl |
126 | This module installs a script called F<staticperl> into your perl |
127 | binary directory. The script is fully self-contained, and can be used |
127 | binary directory. The script is fully self-contained, and can be |
128 | without perl (for example, in an uClibc chroot environment). In fact, |
128 | used without perl (for example, in an uClibc chroot environment). In |
129 | it can be extracted from the C<App::Staticperl> distribution tarball as |
129 | fact, it can be extracted from the C<App::Staticperl> distribution |
130 | F<bin/staticperl>, without any installation. |
130 | tarball as F<bin/staticperl>, without any installation. The |
|
|
131 | newest (possibly alpha) version can also be downloaded from |
|
|
132 | L<http://staticperl.schmorp.de/staticperl>. |
131 | |
133 | |
132 | F<staticperl> interprets the first argument as a command to execute, |
134 | F<staticperl> interprets the first argument as a command to execute, |
133 | optionally followed by any parameters. |
135 | optionally followed by any parameters. |
134 | |
136 | |
135 | There are two command categories: the "phase 1" commands which deal with |
137 | There are two command categories: the "phase 1" commands which deal with |
… | |
… | |
1051 | PERL_CONFIGURE="$PERL_CONFIGURE -U$sym" |
1053 | PERL_CONFIGURE="$PERL_CONFIGURE -U$sym" |
1052 | done |
1054 | done |
1053 | } |
1055 | } |
1054 | |
1056 | |
1055 | This mostly gains space when linking staticaly, as the functions will |
1057 | This mostly gains space when linking staticaly, as the functions will |
1056 | liekly not be linked in. The gain for dynamically-linked binaries is |
1058 | likely not be linked in. The gain for dynamically-linked binaries is |
1057 | smaller. |
1059 | smaller. |
1058 | |
1060 | |
1059 | Also, this leaves C<gethostbyname> in - not only is it actually used |
1061 | Also, this leaves C<gethostbyname> in - not only is it actually used |
1060 | often, the L<Socket> module also exposes it, so leaving it out usually |
1062 | often, the L<Socket> module also exposes it, so leaving it out usually |
1061 | gains little. Why Socket exposes a C function that is in the core already |
1063 | gains little. Why Socket exposes a C function that is in the core already |