… | |
… | |
9 | staticperl configure # fetch and then configure perl |
9 | staticperl configure # fetch and then configure perl |
10 | staticperl build # configure and then build perl |
10 | staticperl build # configure and then build perl |
11 | staticperl install # build and then install perl |
11 | staticperl install # build and then install perl |
12 | staticperl clean # clean most intermediate files (restart at configure) |
12 | staticperl clean # clean most intermediate files (restart at configure) |
13 | staticperl distclean # delete everything installed by this script |
13 | staticperl distclean # delete everything installed by this script |
|
|
14 | staticperl perl ... # invoke the perlinterpreter |
14 | staticperl cpan # invoke CPAN shell |
15 | staticperl cpan # invoke CPAN shell |
15 | staticperl instmod path... # install unpacked modules |
16 | staticperl instmod path... # install unpacked modules |
16 | staticperl instcpan modulename... # install modules from CPAN |
17 | staticperl instcpan modulename... # install modules from CPAN |
17 | staticperl mkbundle <bundle-args...> # see documentation |
18 | staticperl mkbundle <bundle-args...> # see documentation |
18 | staticperl mkperl <bundle-args...> # see documentation |
19 | staticperl mkperl <bundle-args...> # see documentation |
… | |
… | |
20 | |
21 | |
21 | Typical Examples: |
22 | Typical Examples: |
22 | |
23 | |
23 | staticperl install # fetch, configure, build and install perl |
24 | staticperl install # fetch, configure, build and install perl |
24 | staticperl cpan # run interactive cpan shell |
25 | staticperl cpan # run interactive cpan shell |
25 | staticperl mkperl -M '"Config_heavy.pl"' # build a perl that supports -V |
26 | staticperl mkperl -MConfig_heavy.pl # build a perl that supports -V |
26 | staticperl mkperl -MAnyEvent::Impl::Perl -MAnyEvent::HTTPD -MURI -MURI::http |
27 | staticperl mkperl -MAnyEvent::Impl::Perl -MAnyEvent::HTTPD -MURI -MURI::http |
27 | # build a perl with the above modules linked in |
28 | # build a perl with the above modules linked in |
28 | staticperl mkapp myapp --boot mainprog mymodules |
29 | staticperl mkapp myapp --boot mainprog mymodules |
29 | # build a binary "myapp" from mainprog and mymodules |
30 | # build a binary "myapp" from mainprog and mymodules |
30 | |
31 | |
… | |
… | |
38 | file that contains perl interpreter, libc, all the modules you need, all |
39 | file that contains perl interpreter, libc, all the modules you need, all |
39 | the libraries you need and of course your actual program. |
40 | the libraries you need and of course your actual program. |
40 | |
41 | |
41 | With F<uClibc> and F<upx> on x86, you can create a single 500kb binary |
42 | With F<uClibc> and F<upx> on x86, you can create a single 500kb binary |
42 | that contains perl and 100 modules such as POSIX, AnyEvent, EV, IO::AIO, |
43 | that contains perl and 100 modules such as POSIX, AnyEvent, EV, IO::AIO, |
43 | Coro and so on. Or any other choice of modules. |
44 | Coro and so on. Or any other choice of modules (and some other size :). |
44 | |
45 | |
45 | To see how this turns out, you can try out smallperl and bigperl, two |
46 | To see how this turns out, you can try out smallperl and bigperl, two |
46 | pre-built static and compressed perl binaries with many and even more |
47 | pre-built static and compressed perl binaries with many and even more |
47 | modules: just follow the links at L<http://staticperl.schmorp.de/>. |
48 | modules: just follow the links at L<http://staticperl.schmorp.de/>. |
48 | |
49 | |
… | |
… | |
186 | =item F<staticperl install> |
187 | =item F<staticperl install> |
187 | |
188 | |
188 | Wipes the perl installation directory (usually F<~/.staticperl/perl>) and |
189 | Wipes the perl installation directory (usually F<~/.staticperl/perl>) and |
189 | installs the perl distribution, potentially after building it first. |
190 | installs the perl distribution, potentially after building it first. |
190 | |
191 | |
|
|
192 | =item F<staticperl perl> [args...] |
|
|
193 | |
|
|
194 | Invokes the compiled perl interpreter with the given args. Basically the |
|
|
195 | same as starting perl directly (usually via F<~/.staticperl/bin/perl>), |
|
|
196 | but beats typing the path sometimes. |
|
|
197 | |
|
|
198 | Example: check that the Gtk2 module is installed and loadable. |
|
|
199 | |
|
|
200 | staticperl perl -MGtk2 -e0 |
|
|
201 | |
191 | =item F<staticperl cpan> [args...] |
202 | =item F<staticperl cpan> [args...] |
192 | |
203 | |
193 | Starts an interactive CPAN shell that you can use to install further |
204 | Starts an interactive CPAN shell that you can use to install further |
194 | modules. Installs the perl first if necessary, but apart from that, |
205 | modules. Installs the perl first if necessary, but apart from that, |
195 | no magic is involved: you could just as well run it manually via |
206 | no magic is involved: you could just as well run it manually via |
… | |
… | |
252 | |
263 | |
253 | # first make sure we have perl and the required modules |
264 | # first make sure we have perl and the required modules |
254 | staticperl instcpan AnyEvent::HTTPD |
265 | staticperl instcpan AnyEvent::HTTPD |
255 | |
266 | |
256 | # now build the perl |
267 | # now build the perl |
257 | staticperl mkperl -M'"Config_heavy.pl"' -MAnyEvent::Impl::Perl \ |
268 | staticperl mkperl -MConfig_heavy.pl -MAnyEvent::Impl::Perl \ |
258 | -MAnyEvent::HTTPD -MURI::http \ |
269 | -MAnyEvent::HTTPD -MURI::http \ |
259 | --add 'eg/httpd httpd.pm' |
270 | --add 'eg/httpd httpd.pm' |
260 | |
271 | |
261 | # finally, invoke it |
272 | # finally, invoke it |
262 | ./perl -Mhttpd |
273 | ./perl -Mhttpd |
… | |
… | |
381 | |
392 | |
382 | =over 4 |
393 | =over 4 |
383 | |
394 | |
384 | =item C<--use> F<module> | C<-M>F<module> |
395 | =item C<--use> F<module> | C<-M>F<module> |
385 | |
396 | |
386 | Include the named module and trace direct dependencies. This is done by |
397 | Include the named module or perl library and trace direct |
387 | C<use>'ing the module from a fresh package in a subprocess and tracing |
398 | dependencies. This is done by loading the module in a subprocess and |
388 | which other modules and files it actually loads. |
399 | tracing which other modules and files it actually loads. |
389 | |
400 | |
390 | Example: include AnyEvent and AnyEvent::Impl::Perl. |
401 | Example: include AnyEvent and AnyEvent::Impl::Perl. |
391 | |
402 | |
392 | staticperl mkbundle --use AnyEvent --use AnyEvent::Impl::Perl |
403 | staticperl mkbundle --use AnyEvent --use AnyEvent::Impl::Perl |
393 | |
404 | |
394 | Sometimes you want to load old-style "perl libraries" (F<.pl> files), |
405 | Sometimes you want to load old-style "perl libraries" (F<.pl> files), or |
395 | or maybe other weirdly named files. To do that, you need to quote |
406 | maybe other weirdly named files. To support this, the C<--use> option |
396 | the name in single or double quotes (this is because F<staticperl> |
407 | actually tries to do what you mean, depending on the string you specify: |
397 | I<literally> just adds the string after the C<require> - which acts |
408 | |
398 | different when confronted with quoted vs. unquoted strings). When given on |
409 | =over 4 |
399 | the command line, you probably need to quote once more to avoid your shell |
410 | |
400 | interpreting it. Common cases that need this are F<Config_heavy.pl> and |
411 | =item a possibly valid module name, e.g. F<common::sense>, F<Carp>, |
401 | F<utf8_heavy.pl>. |
412 | F<Coro::Mysql>. |
|
|
413 | |
|
|
414 | If the string contains no quotes, no F</> and no F<.>, then C<--use> |
|
|
415 | assumes that it is a normal module name. It will create a new package and |
|
|
416 | evaluate a C<use module> in it, i.e. it will load the package and do a |
|
|
417 | default import. |
|
|
418 | |
|
|
419 | The import step is done because many modules trigger more dependencies |
|
|
420 | when something is imported than without. |
|
|
421 | |
|
|
422 | =item anything that contains F</> or F<.> characters, |
|
|
423 | e.g. F<utf8_heavy.pl>, F<Module/private/data.pl>. |
|
|
424 | |
|
|
425 | The string will be quoted and passed to require, as if you used C<require |
|
|
426 | $module>. Nothing will be imported. |
|
|
427 | |
|
|
428 | =item "path" or 'path', e.g. C<"utf8_heavy.pl">. |
|
|
429 | |
|
|
430 | If you enclose the name into single or double quotes, then the quotes will |
|
|
431 | be removed and the resulting string will be passed to require. This syntax |
|
|
432 | is form compatibility with older versions of staticperl and should not be |
|
|
433 | used anymore. |
|
|
434 | |
|
|
435 | =back |
|
|
436 | |
|
|
437 | Example: C<use> AnyEvent::Socket, once using C<use> (importing the |
|
|
438 | symbols), and once via C<require>, not importing any symbols. The first |
|
|
439 | form is preferred as many modules load some extra dependencies when asked |
|
|
440 | to export symbols. |
|
|
441 | |
|
|
442 | staticperl mkbundle -MAnyEvent::Socket # use + import |
|
|
443 | staticperl mkbundle -MAnyEvent/Socket.pm # require only |
402 | |
444 | |
403 | Example: include the required files for F<perl -V> to work in all its |
445 | Example: include the required files for F<perl -V> to work in all its |
404 | glory (F<Config.pm> is included automatically by this). |
446 | glory (F<Config.pm> is included automatically by the dependency tracker). |
405 | |
447 | |
406 | # bourne shell |
448 | # shell command |
407 | staticperl mkbundle --use '"Config_heavy.pl"' |
449 | staticperl mkbundle -MConfig_heavy.pl |
408 | |
450 | |
409 | # bundle specification file |
451 | # bundle specification file |
410 | use "Config_heavy.pl" |
452 | use Config_heavy.pl |
411 | |
453 | |
412 | The C<-M>module syntax is included as a convenience that might be easier |
454 | The C<-M>module syntax is included as a convenience that might be easier |
413 | to remember than C<--use> - it's the same switch as perl itself uses |
455 | to remember than C<--use> - it's the same switch as perl itself uses |
414 | to load modules. Or maybe it confuses people. Time will tell. Or maybe |
456 | to load modules. Or maybe it confuses people. Time will tell. Or maybe |
415 | not. Sigh. |
457 | not. Sigh. |
… | |
… | |
681 | Example: create a standalone perl binary called F<./myexe> that will |
723 | Example: create a standalone perl binary called F<./myexe> that will |
682 | execute F<appfile> when it is started. |
724 | execute F<appfile> when it is started. |
683 | |
725 | |
684 | staticperl mkbundle --app myexe --boot appfile |
726 | staticperl mkbundle --app myexe --boot appfile |
685 | |
727 | |
|
|
728 | =item C<--ignore-env> |
|
|
729 | |
|
|
730 | Generates extra code to unset some environment variables before |
|
|
731 | initialising/running perl. Perl supports a lot of environment variables |
|
|
732 | that might alter execution in ways that might be undesirablre for |
|
|
733 | standalone applications, and this option removes those known to cause |
|
|
734 | trouble. |
|
|
735 | |
|
|
736 | Specifically, these are removed: |
|
|
737 | |
|
|
738 | C<PERL_HASH_SEED_DEBUG> and C<PERL_DEBUG_MSTATS> can cause underaible |
|
|
739 | output, C<PERL5OPT>, C<PERL_DESTRUCT_LEVEL>, C<PERL_HASH_SEED> and |
|
|
740 | C<PERL_SIGNALS> can alter execution significantly, and C<PERL_UNICODE>, |
|
|
741 | C<PERLIO_DEBUG> and C<PERLIO> can affect input and output. |
|
|
742 | |
|
|
743 | The variables C<PERL_LIB> and C<PERL5_LIB> are always ignored because the |
|
|
744 | startup code used by F<staticperl> overrides C<@INC> in all cases. |
|
|
745 | |
|
|
746 | This option will not make your program more secure (unless you are |
|
|
747 | running with elevated privileges), but it will reduce the surprise effect |
|
|
748 | when a user has these environment variables set and doesn't expect your |
|
|
749 | standalone program to act like a perl interpreter. |
|
|
750 | |
686 | =item C<--static> |
751 | =item C<--static> |
687 | |
752 | |
688 | Add C<-static> to F<bundle.ldopts>, which means a fully static (if |
753 | Add C<-static> to F<bundle.ldopts>, which means a fully static (if |
689 | supported by the OS) executable will be created. This is not immensely |
754 | supported by the OS) executable will be created. This is not immensely |
690 | useful when just creating the bundle files, but is most useful when |
755 | useful when just creating the bundle files, but is most useful when |
… | |
… | |
817 | =item C<STATICPERL> |
882 | =item C<STATICPERL> |
818 | |
883 | |
819 | The directory where staticperl stores all its files |
884 | The directory where staticperl stores all its files |
820 | (default: F<~/.staticperl>). |
885 | (default: F<~/.staticperl>). |
821 | |
886 | |
|
|
887 | =item C<DLCACHE> |
|
|
888 | |
|
|
889 | The path to a directory (will be created if it doesn't exist) where |
|
|
890 | downloaded perl sources are being cached, to avoid downloading them |
|
|
891 | again. The default is empty, which means there is no cache. |
|
|
892 | |
|
|
893 | =item C<PERL_VERSION> |
|
|
894 | |
|
|
895 | The perl version to install - default is currently C<5.12.3>, but C<5.8.9> |
|
|
896 | is also a good choice (5.8.9 is much smaller than 5.12.3, while 5.10.1 is |
|
|
897 | about as big as 5.12.3). |
|
|
898 | |
822 | =item C<PERL_MM_USE_DEFAULT>, C<EV_EXTRA_DEFS>, ... |
899 | =item C<PERL_MM_USE_DEFAULT>, C<EV_EXTRA_DEFS>, ... |
823 | |
900 | |
824 | Usually set to C<1> to make modules "less inquisitive" during their |
901 | Usually set to C<1> to make modules "less inquisitive" during their |
825 | installation, you can set any environment variable you want - some modules |
902 | installation, you can set any environment variable you want - some modules |
826 | (such as L<Coro> or L<EV>) use environment variables for further tweaking. |
903 | (such as L<Coro> or L<EV>) use environment variables for further tweaking. |
827 | |
|
|
828 | =item C<PERL_VERSION> |
|
|
829 | |
|
|
830 | The perl version to install - default is currently C<5.12.3>, but C<5.8.9> |
|
|
831 | is also a good choice (5.8.9 is much smaller than 5.12.3, while 5.10.1 is |
|
|
832 | about as big as 5.12.3). |
|
|
833 | |
904 | |
834 | =item C<PERL_PREFIX> |
905 | =item C<PERL_PREFIX> |
835 | |
906 | |
836 | The prefix where perl gets installed (default: F<$STATICPERL/perl>), |
907 | The prefix where perl gets installed (default: F<$STATICPERL/perl>), |
837 | i.e. where the F<bin> and F<lib> subdirectories will end up. |
908 | i.e. where the F<bin> and F<lib> subdirectories will end up. |
… | |
… | |
858 | F<~/.staticperlrc> to override them. |
929 | F<~/.staticperlrc> to override them. |
859 | |
930 | |
860 | Most of the variables override (or modify) the corresponding F<Configure> |
931 | Most of the variables override (or modify) the corresponding F<Configure> |
861 | variable, except C<PERL_CCFLAGS>, which gets appended. |
932 | variable, except C<PERL_CCFLAGS>, which gets appended. |
862 | |
933 | |
|
|
934 | You should have a look near the beginning of the F<staticperl> script - |
|
|
935 | staticperl tries to default C<PERL_OPTIMIZE> to some psace-saving options |
|
|
936 | suitable for newer gcc versions. For other compilers or older versions you |
|
|
937 | need to adjust these, for example, in your F<~/.staticperlrc>. |
|
|
938 | |
863 | =back |
939 | =back |
864 | |
940 | |
865 | =head4 Variables you probably I<do not want> to override |
941 | =head4 Variables you probably I<do not want> to override |
866 | |
942 | |
867 | =over 4 |
943 | =over 4 |
… | |
… | |
885 | =head3 OVERRIDABLE HOOKS |
961 | =head3 OVERRIDABLE HOOKS |
886 | |
962 | |
887 | In addition to environment variables, it is possible to provide some |
963 | In addition to environment variables, it is possible to provide some |
888 | shell functions that are called at specific times. To provide your own |
964 | shell functions that are called at specific times. To provide your own |
889 | commands, just define the corresponding function. |
965 | commands, just define the corresponding function. |
|
|
966 | |
|
|
967 | The actual order in which hooks are invoked during a full install |
|
|
968 | from scratch is C<preconfigure>, C<patchconfig>, C<postconfigure>, |
|
|
969 | C<postbuild>, C<postinstall>. |
890 | |
970 | |
891 | Example: install extra modules from CPAN and from some directories |
971 | Example: install extra modules from CPAN and from some directories |
892 | at F<staticperl install> time. |
972 | at F<staticperl install> time. |
893 | |
973 | |
894 | postinstall() { |
974 | postinstall() { |
… | |
… | |
901 | |
981 | |
902 | =over 4 |
982 | =over 4 |
903 | |
983 | |
904 | =item preconfigure |
984 | =item preconfigure |
905 | |
985 | |
906 | Called just before running F<./Configur> in the perl source |
986 | Called just before running F<./Configure> in the perl source |
907 | directory. Current working directory is the perl source directory. |
987 | directory. Current working directory is the perl source directory. |
908 | |
988 | |
909 | This can be used to set any C<PERL_xxx> variables, which might be costly |
989 | This can be used to set any C<PERL_xxx> variables, which might be costly |
910 | to compute. |
990 | to compute. |
911 | |
991 | |
|
|
992 | =item patchconfig |
|
|
993 | |
|
|
994 | Called after running F<./Configure> in the perl source directory to create |
|
|
995 | F<./config.sh>, but before running F<./Configure -S> to actually apply the |
|
|
996 | config. Current working directory is the perl source directory. |
|
|
997 | |
|
|
998 | Can be used to tailor/patch F<config.sh> or do any other modifications. |
|
|
999 | |
912 | =item postconfigure |
1000 | =item postconfigure |
913 | |
1001 | |
914 | Called after configuring, but before building perl. Current working |
1002 | Called after configuring, but before building perl. Current working |
915 | directory is the perl source directory. |
1003 | directory is the perl source directory. |
916 | |
|
|
917 | Could be used to tailor/patch config.sh (followed by F<sh Configure -S>) |
|
|
918 | or do any other modifications. |
|
|
919 | |
1004 | |
920 | =item postbuild |
1005 | =item postbuild |
921 | |
1006 | |
922 | Called after building, but before installing perl. Current working |
1007 | Called after building, but before installing perl. Current working |
923 | directory is the perl source directory. |
1008 | directory is the perl source directory. |
… | |
… | |
1076 | good experiences with GCC 4.4.x but not GCC 4.5. |
1161 | good experiences with GCC 4.4.x but not GCC 4.5. |
1077 | |
1162 | |
1078 | To minimise code size, I used C<-pipe -ffunction-sections -fdata-sections |
1163 | To minimise code size, I used C<-pipe -ffunction-sections -fdata-sections |
1079 | -finline-limit=8 -fno-builtin-strlen -mtune=i386>. The C<-mtune=i386> |
1164 | -finline-limit=8 -fno-builtin-strlen -mtune=i386>. The C<-mtune=i386> |
1080 | doesn't decrease codesize much, but it makes the file much more |
1165 | doesn't decrease codesize much, but it makes the file much more |
1081 | compressible. |
1166 | compressible (and the execution a lot slower...). |
1082 | |
1167 | |
1083 | If you don't need Coro or threads, you can go with "linuxthreads.old" (or |
1168 | If you don't need Coro or threads, you can go with "linuxthreads.old" (or |
1084 | no thread support). For Coro, it is highly recommended to switch to a |
1169 | no thread support). For Coro, it is highly recommended to switch to a |
1085 | uClibc newer than 0.9.31 (at the time of this writing, I used the 20101201 |
1170 | uClibc newer than 0.9.31 (at the time of this writing, I used the 20101201 |
1086 | snapshot) and enable NPTL, otherwise Coro needs to be configured with the |
1171 | snapshot) and enable NPTL, otherwise Coro needs to be configured with the |
… | |
… | |
1088 | twice the address space needed for stacks). |
1173 | twice the address space needed for stacks). |
1089 | |
1174 | |
1090 | If you use C<linuxthreads.old>, then you should also be aware that |
1175 | If you use C<linuxthreads.old>, then you should also be aware that |
1091 | uClibc shares C<errno> between all threads when statically linking. See |
1176 | uClibc shares C<errno> between all threads when statically linking. See |
1092 | L<http://lists.uclibc.org/pipermail/uclibc/2010-June/044157.html> for a |
1177 | L<http://lists.uclibc.org/pipermail/uclibc/2010-June/044157.html> for a |
1093 | workaround (And L<https://bugs.uclibc.org/2089> for discussion). |
1178 | workaround (and L<https://bugs.uclibc.org/2089> for discussion). |
1094 | |
1179 | |
1095 | C<ccache> support is also recommended, especially if you want |
1180 | C<ccache> support is also recommended, especially if you want |
1096 | to play around with buildroot options. Enabling the C<miniperl> |
1181 | to play around with buildroot options. Enabling the C<miniperl> |
1097 | package will probably enable all options required for a successful |
1182 | package will probably enable all options required for a successful |
1098 | perl build. F<staticperl> itself additionally needs either C<wget> |
1183 | perl build. F<staticperl> itself additionally needs either C<wget> |
… | |
… | |
1106 | it from working properly in a chroot - either use dash (and link it to |
1191 | it from working properly in a chroot - either use dash (and link it to |
1107 | F</bin/sh> inside the chroot) or link busybox to F</bin/sh>, using it's |
1192 | F</bin/sh> inside the chroot) or link busybox to F</bin/sh>, using it's |
1108 | built-in ash shell. |
1193 | built-in ash shell. |
1109 | |
1194 | |
1110 | Finally, you need F</dev/null> inside the chroot for many scripts to work |
1195 | Finally, you need F</dev/null> inside the chroot for many scripts to work |
1111 | - F<cp /dev/null output/target/dev> or bind-mounting your F</dev> will |
1196 | - either F<cp /dev/null output/target/dev> or bind-mounting your F</dev> |
1112 | both provide this. |
1197 | will provide this. |
1113 | |
1198 | |
1114 | After you have compiled and set up your buildroot target, you can copy |
1199 | After you have compiled and set up your buildroot target, you can copy |
1115 | F<staticperl> from the C<App::Staticperl> distribution or from your |
1200 | F<staticperl> from the C<App::Staticperl> distribution or from your |
1116 | perl f<bin> directory (if you installed it) into the F<output/target> |
1201 | perl F<bin> directory (if you installed it) into the F<output/target> |
1117 | filesystem, chroot inside and run it. |
1202 | filesystem, chroot inside and run it. |
1118 | |
1203 | |
1119 | =head1 RECIPES / SPECIFIC MODULES |
1204 | =head1 RECIPES / SPECIFIC MODULES |
1120 | |
1205 | |
1121 | This section contains some common(?) recipes and information about |
1206 | This section contains some common(?) recipes and information about |
… | |
… | |
1130 | |
1215 | |
1131 | Some functionality in the utf8 module, such as swash handling (used |
1216 | Some functionality in the utf8 module, such as swash handling (used |
1132 | for unicode character ranges in regexes) is implemented in the |
1217 | for unicode character ranges in regexes) is implemented in the |
1133 | C<"utf8_heavy.pl"> library: |
1218 | C<"utf8_heavy.pl"> library: |
1134 | |
1219 | |
1135 | -M'"utf8_heavy.pl"' |
1220 | -Mutf8_heavy.pl |
1136 | |
1221 | |
1137 | Many Unicode properties in turn are defined in separate modules, |
1222 | Many Unicode properties in turn are defined in separate modules, |
1138 | such as C<"unicore/Heavy.pl"> and more specific data tables such as |
1223 | such as C<"unicore/Heavy.pl"> and more specific data tables such as |
1139 | C<"unicore/To/Digit.pl"> or C<"unicore/lib/Perl/Word.pl">. These tables |
1224 | C<"unicore/To/Digit.pl"> or C<"unicore/lib/Perl/Word.pl">. These tables |
1140 | are big (7MB uncompressed, although F<staticperl> contains special |
1225 | are big (7MB uncompressed, although F<staticperl> contains special |
… | |
… | |
1159 | C<"AnyEvent/Util/uts46data.pl">. |
1244 | C<"AnyEvent/Util/uts46data.pl">. |
1160 | |
1245 | |
1161 | Or you can use C<--usepacklists> and specify C<-MAnyEvent> to include |
1246 | Or you can use C<--usepacklists> and specify C<-MAnyEvent> to include |
1162 | everything. |
1247 | everything. |
1163 | |
1248 | |
|
|
1249 | =item Cairo |
|
|
1250 | |
|
|
1251 | See Glib, same problem, same solution. |
|
|
1252 | |
1164 | =item Carp |
1253 | =item Carp |
1165 | |
1254 | |
1166 | Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of |
1255 | Carp had (in older versions of perl) a dependency on L<Carp::Heavy>. As of |
1167 | perl 5.12.2 (maybe earlier), this dependency no longer exists. |
1256 | perl 5.12.2 (maybe earlier), this dependency no longer exists. |
1168 | |
1257 | |
1169 | =item Config |
1258 | =item Config |
1170 | |
1259 | |
1171 | The F<perl -V> switch (as well as many modules) needs L<Config>, which in |
1260 | The F<perl -V> switch (as well as many modules) needs L<Config>, which in |
1172 | turn might need L<"Config_heavy.pl">. Including the latter gives you |
1261 | turn might need L<"Config_heavy.pl">. Including the latter gives you |
1173 | both. |
1262 | both. |
|
|
1263 | |
|
|
1264 | =item Glib |
|
|
1265 | |
|
|
1266 | Glib literally requires Glib to be installed already to build - it tries |
|
|
1267 | to fake this by running Glib out of the build directory before being |
|
|
1268 | built. F<staticperl> tries to work around this by forcing C<MAN1PODS> and |
|
|
1269 | C<MAN3PODS> to be empty via the C<PERL_MM_OPT> environment variable. |
|
|
1270 | |
|
|
1271 | =item Gtk2 |
|
|
1272 | |
|
|
1273 | See Pango, same problems, same solution. |
|
|
1274 | |
|
|
1275 | =item Pango |
|
|
1276 | |
|
|
1277 | In addition to the C<MAN3PODS> problem in Glib, Pango also routes around |
|
|
1278 | L<ExtUtils::MakeMaker> by compiling its files on its own. F<staticperl> |
|
|
1279 | tries to patch L<ExtUtils::MM_Unix> to route around Pango. |
1174 | |
1280 | |
1175 | =item Term::ReadLine::Perl |
1281 | =item Term::ReadLine::Perl |
1176 | |
1282 | |
1177 | Also needs L<Term::ReadLine::readline>, or C<--usepacklists>. |
1283 | Also needs L<Term::ReadLine::readline>, or C<--usepacklists>. |
1178 | |
1284 | |