[ViewVC] Diff of: cvs/App-Staticperl/staticperl.pod

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.47 by root, Sat Jul 9 18:26:27 2011 UTC vs.
Revision 1.66 by root, Fri Aug 4 03:14:33 2023 UTC

…		…
1	=head1 NAME	1	=head1 NAME
2		2
3	staticperl - perl, libc, 100 modules, all in one 500kb file	3	staticperl - perl, libc, 100 modules, all in one standalone 500kb file
4		4
5	=head1 SYNOPSIS	5	=head1 SYNOPSIS
6		6
7	staticperl help # print the embedded documentation	7	staticperl help # print the embedded documentation
8	staticperl fetch # fetch and unpack perl sources	8	staticperl fetch # fetch and unpack perl sources
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 perl ... # invoke the perlinterpreter
15	staticperl cpan # invoke CPAN shell	15	staticperl cpan # invoke CPAN shell
16	staticperl instmod path... # install unpacked modules	16	staticperl instsrc path... # install unpacked modules
17	staticperl instcpan modulename... # install modules from CPAN	17	staticperl instcpan modulename... # install modules from CPAN
18	staticperl mkbundle <bundle-args...> # see documentation	18	staticperl mkbundle <bundle-args...> # see documentation
19	staticperl mkperl <bundle-args...> # see documentation	19	staticperl mkperl <bundle-args...> # see documentation
20	staticperl mkapp appname <bundle-args...> # see documentation	20	staticperl mkapp appname <bundle-args...> # see documentation
21		21
…		…
348	add eg/httpd httpd.pm	348	add eg/httpd httpd.pm
349		349
350	All options that specify modules or files to be added are processed in the	350	All options that specify modules or files to be added are processed in the
351	order given on the command line.	351	order given on the command line.
352		352
353	=head3 BUNDLE CREATION WORKFLOW / STATICPELR MKBUNDLE OPTIONS	353	=head3 BUNDLE CREATION WORKFLOW / STATICPERL MKBUNDLE OPTIONS
354		354
355	F<staticperl mkbundle> works by first assembling a list of candidate	355	F<staticperl mkbundle> works by first assembling a list of candidate
356	files and modules to include, then filtering them by include/exclude	356	files and modules to include, then filtering them by include/exclude
357	patterns. The remaining modules (together with their direct dependencies,	357	patterns. The remaining modules (together with their direct dependencies,
358	such as link libraries and L<AutoLoader> files) are then converted into	358	such as link libraries and L<AutoLoader> files) are then converted into
…		…
543	# then later, in perl, use	543	# then later, in perl, use
544	use myfiles::file1;	544	use myfiles::file1;
545	require myfiles::file2;	545	require myfiles::file2;
546	my $res = do "myfiles/file3.pl";	546	my $res = do "myfiles/file3.pl";
547		547
548	=item C<--binadd> F<file> \| C<--add> "F<file> alias"	548	=item C<--addbin> F<file> \| C<--addbin> "F<file> alias"
549		549
550	Just like C<--add>, except that it treats the file as binary and adds it	550	Just like C<--add>, except that it treats the file as binary and adds it
551	without any postprocessing (perl files might get stripped to reduce their	551	without any postprocessing (perl files might get stripped to reduce their
552	size).	552	size).
553		553
554	If you specify an alias you should probably add a C<&> prefix to avoid	554	If you specify an alias you should probably add a C</> prefix to avoid
555	clashing with embedded perl files (whose paths never start with C<&>),	555	clashing with embedded perl files (whose paths never start with C</>),
556	and/or use a special directory prefix, such as C<&res/name>.	556	and/or use a special directory prefix, such as C</res/name>.
557		557
558	You can later get a copy of these files by calling C<staticperl::find	558	You can later get a copy of these files by calling C<static::find
559	"alias">.	559	"alias">.
560		560
561	An alternative way to embed binary files is to convert them to perl and	561	An alternative way to embed binary files is to convert them to perl and
562	use C<do> to get the contents - this method is a bit cumbersome, but works	562	use C<do> to get the contents - this method is a bit cumbersome, but works
563	both inside and outside of a staticperl bundle:	563	both inside and outside of a staticperl bundle, without extra ado:
564		564
565	# a "binary" file, call it "bindata.pl"	565	# a "binary" file, call it "bindata.pl"
566	<<'SOME_MARKER'	566	<<'SOME_MARKER'
567	binary data NOT containing SOME_MARKER	567	binary data NOT containing SOME_MARKER
568	SOME_MARKER	568	SOME_MARKER
569		569
570	# load the binary	570	# load the binary
571	chomp (my $data = do "bindata.pl");	571	chomp (my $data = do "bindata.pl");
572		572
573	=item C<--allow-dlls>	573	=item C<--allow-dynamic>
574		574
575	By default, when F<mkbundle> hits a dynamic perl extension (e.g. a F<.so>	575	By default, when F<mkbundle> hits a dynamic perl extension (e.g. a F<.so>
576	or F<.dll> file), it will stop with a fatal error.	576	or F<.dll> file), it will stop with a fatal error.
577		577
578	This option instead packages the shared object into the bundle, with a	578	When this option is enabled, F<mkbundle> packages the shared
579	prefix of F<&fs/perl/> (e.g. F<&fs/perl/auto/List/Util/Util.so>). What you	579	object into the bundle instead, with a prefix of F<!>
580	do with that is up to you, F<staticperl> has no special support for this	580	(e.g. F<!auto/List/Util/Util.so>). What you do with that is currently up
581	at the moment, apart from working around the lack of availability of	581	to you, F<staticperl> has no special support for this at the moment, apart
582	F<PerlIO::scalar> while bootstrapping, at a speed cost.	582	from working around the lack of availability of F<PerlIO::scalar> while
		583	bootstrapping, at a speed cost.
583		584
584	One way to deal with this is to write all files starting with F<&fs/> into	585	One way to deal with this is to write all files starting with F<!> into
585	some directory and C<unshift>ing the path corresponding to F<&fs/perl/>	586	some directory and then C<unshift> that path onto C<@INC>.
586	onto C<@INC>.
587		587
588	#TODO: example	588	#TODO: example
589		589
590	=back	590	=back
591		591
…		…
704	Last not least, if you need accurate line numbers in error messages,	704	Last not least, if you need accurate line numbers in error messages,
705	or in the unlikely case where C<pod> is too slow, or some module gets	705	or in the unlikely case where C<pod> is too slow, or some module gets
706	mistreated, you can specify C<none> to not mangle included perl sources in	706	mistreated, you can specify C<none> to not mangle included perl sources in
707	any way.	707	any way.
708		708
		709	=item C<--compress> C<none>\|C<lzf>
		710
		711	Compress each included library file with C<lzf> (default), or do not
		712	compress (C<none>). LZF compression typically halves the size of the
		713	included library data at almost no overhead, but is counterproductive if
		714	you are using another compression solution such as C<UPX>, so it cna be
		715	disabled.
		716
709	=item C<--perl>	717	=item C<--perl>
710		718
711	After writing out the bundle files, try to link a new perl interpreter. It	719	After writing out the bundle files, try to link a new perl interpreter. It
712	will be called F<perl> and will be left in the current working	720	will be called F<perl> and will be left in the current working
713	directory. The bundle files will be removed.	721	directory. The bundle files will be removed.
…		…
752	standalone applications, and this option removes those known to cause	760	standalone applications, and this option removes those known to cause
753	trouble.	761	trouble.
754		762
755	Specifically, these are removed:	763	Specifically, these are removed:
756		764
757	C<PERL_HASH_SEED_DEBUG> and C<PERL_DEBUG_MSTATS> can cause underaible	765	C<PERL_HASH_SEED_DEBUG> and C<PERL_DEBUG_MSTATS> can cause undesirable
758	output, C<PERL5OPT>, C<PERL_DESTRUCT_LEVEL>, C<PERL_HASH_SEED> and	766	output, C<PERL5OPT>, C<PERL_DESTRUCT_LEVEL>, C<PERL_HASH_SEED> and
759	C<PERL_SIGNALS> can alter execution significantly, and C<PERL_UNICODE>,	767	C<PERL_SIGNALS> can alter execution significantly, and C<PERL_UNICODE>,
760	C<PERLIO_DEBUG> and C<PERLIO> can affect input and output.	768	C<PERLIO_DEBUG> and C<PERLIO> can affect input and output.
761		769
762	The variables C<PERL_LIB> and C<PERL5_LIB> are always ignored because the	770	The variables C<PERL_LIB> and C<PERL5_LIB> are always ignored because the
…		…
800	staticperl mkperl -MIO::AIO --staticlib crypt	808	staticperl mkperl -MIO::AIO --staticlib crypt
801		809
802	# ldopts might now contain:	810	# ldopts might now contain:
803	# -lm -Wl,-Bstatic -lcrypt -Wl,-Bdynamic -lpthread	811	# -lm -Wl,-Bstatic -lcrypt -Wl,-Bdynamic -lpthread
804		812
		813	=item C<--extra-cflags> string
		814
		815	Specifies extra compiler flags, used when compiling the bundle file. The
		816	flags are appended to all the existing flags, so can be sued to override
		817	settings.
		818
		819	=item C<--extra-ldflags> string
		820
		821	Specifies extra linker flags, used when linking the bundle.
		822
		823	=item C<--extra-libs> string
		824
		825	Extra linker flags, appended at the end when linking. The difference to
		826	C<--extra-ldflags> is that the ldflags are appended to the flags, before
		827	the objects and libraries, and the extra libs are added at the end.
		828
805	=back	829	=back
806		830
807	=back	831	=back
808		832
809	=head3 EXTENDED GLOB PATTERNS	833	=head3 EXTENDED GLOB PATTERNS
…		…
909	downloaded perl sources are being cached, to avoid downloading them	933	downloaded perl sources are being cached, to avoid downloading them
910	again. The default is empty, which means there is no cache.	934	again. The default is empty, which means there is no cache.
911		935
912	=item C<PERL_VERSION>	936	=item C<PERL_VERSION>
913		937
914	The perl version to install - default is currently C<5.12.3>, but C<5.8.9>	938	The perl version to install - C<5.12.5> is a good choice for small builds,
915	is also a good choice (5.8.9 is much smaller than 5.12.3, while 5.10.1 is	939	but C<5.8.9> is also a good choice (5.8.9 is much smaller than 5.12.5), if
916	about as big as 5.12.3).	940	it builds on your system.
		941
		942	You can also set this variable to the absolute URL of a tarball (F<.tar>,
		943	F<.tar.gz>, F<.tar.bz2>, F<.tar.lzma> or F<.tar.xz>), or to the absolute
		944	path of an unpacked perl source tree, which will be copied.
		945
		946	The default is currently
		947	F<http://stableperl.schmorp.de/dist/latest.tar.gz>, i.e. the latest
		948	stableperl release.
917		949
918	=item C<PERL_MM_USE_DEFAULT>, C<EV_EXTRA_DEFS>, ...	950	=item C<PERL_MM_USE_DEFAULT>, C<EV_EXTRA_DEFS>, ...
919		951
920	Usually set to C<1> to make modules "less inquisitive" during their	952	Usually set to C<1> to make modules "less inquisitive" during their
921	installation. You can set (and export!) any environment variable you want	953	installation. You can set (and export!) any environment variable you want
922	- some modules (such as L<Coro> or L<EV>) use environment variables for	954	- some modules (such as L<Coro> or L<EV>) use environment variables for
923	further tweaking.	955	further tweaking.
924		956
925	=item C<PERL_PREFIX>	957	=item C<PERL_PREFIX>
926		958
927	The prefix where perl gets installed (default: F<$STATICPERL/perl>),	959	The directory where perl gets installed (default: F<$STATICPERL/perl>),
928	i.e. where the F<bin> and F<lib> subdirectories will end up.	960	i.e. where the F<bin> and F<lib> subdirectories will end up. Previous
		961	contents will be removed on installation.
929		962
930	=item C<PERL_CONFIGURE>	963	=item C<PERL_CONFIGURE>
931		964
932	Additional Configure options - these are simply passed to the perl	965	Additional Configure options - these are simply passed to the perl
933	Configure script. For example, if you wanted to enable dynamic loading,	966	Configure script. For example, if you wanted to enable dynamic loading,
…		…
949	F<~/.staticperlrc> to override them.	982	F<~/.staticperlrc> to override them.
950		983
951	Most of the variables override (or modify) the corresponding F<Configure>	984	Most of the variables override (or modify) the corresponding F<Configure>
952	variable, except C<PERL_CCFLAGS>, which gets appended.	985	variable, except C<PERL_CCFLAGS>, which gets appended.
953		986
954	You should have a look near the beginning of the F<staticperl> script -	987	The default for C<PERL_OPTIMIZE> is C<-Os> (assuming gcc), and for
955	staticperl tries to default C<PERL_OPTIMIZE> to some psace-saving options	988	C<PERL_LIBS> is C<-lm -lcrypt>, which should be good for most (but not
956	suitable for newer gcc versions. For other compilers or older versions you	989	all) systems.
		990
		991	For other compilers or more customised optimisation settings, you need to
957	need to adjust these, for example, in your F<~/.staticperlrc>.	992	adjust these, e.g. in your F<~/.staticperlrc>.
		993
		994	With gcc on x86 and amd64, you can get more space-savings by using:
		995
		996	-Os -ffunction-sections -fdata-sections -finline-limit=8 -mpush-args
		997	-mno-inline-stringops-dynamically -mno-align-stringops
		998
		999	And on x86 and pentium3 and newer (basically everything you might ever
		1000	want to run on), adding these is even better for space-savings (use
		1001	-mtune=core2 or something newer for much faster code, too):
		1002
		1003	-fomit-frame-pointer -march=pentium3 -mtune=i386
958		1004
959	=back	1005	=back
960		1006
961	=head4 Variables you probably I<do not want> to override	1007	=head4 Variables you probably I<do not want> to override
962		1008
…		…
1027	Called after building, but before installing perl. Current working	1073	Called after building, but before installing perl. Current working
1028	directory is the perl source directory.	1074	directory is the perl source directory.
1029		1075
1030	I have no clue what this could be used for - tell me.	1076	I have no clue what this could be used for - tell me.
1031		1077
		1078	=item postcpanconfig
		1079
		1080	Called just after CPAN has been configured, but before it has been used to
		1081	install anything. You can further change the configuration like this:
		1082
		1083	"$PERL_PREFIX"/bin/perl -MCPAN::MyConfig -MCPAN -e '
		1084	CPAN::Shell->o (conf => urllist => push => "'"$CPAN"'");
		1085	' \|\| fatal "error while initialising CPAN in postcpanconfig"
		1086
1032	=item postinstall	1087	=item postinstall
1033		1088
1034	Called after perl and any extra modules have been installed in C<$PREFIX>,	1089	Called after perl and any extra modules have been installed in C<$PREFIX>,
1035	but before setting the "installation O.K." flag.	1090	but before setting the "installation O.K." flag.
1036		1091
…		…
1141		1196
1142	=back	1197	=back
1143		1198
1144	=head1 RUNTIME FUNCTIONALITY	1199	=head1 RUNTIME FUNCTIONALITY
1145		1200
1146	Binaries created with C<mkbundle>/C<mkperl> contain extra functions, which	1201	Binaries created with C<mkbundle>/C<mkperl> contain extra functionality,
1147	are required to access the bundled perl sources, but might be useful for	1202	mostly related to the extra files bundled in the binary (the virtual
1148	other purposes.	1203	filesystem). All of this data is statically compiled into the binary, and
		1204	accessing means copying it from a read-only section of your binary. Data
		1205	pages in this way are usually freed by the operating system, as they aren't
		1206	used more then once.
		1207
		1208	=head2 VIRTUAL FILESYSTEM
		1209
		1210	Every bundle has a virtual filesystem. The only information stored in it
		1211	is the path and contents of each file that was bundled.
		1212
		1213	=head3 LAYOUT
		1214
		1215	Any paths starting with an ampersand (F<&>) or exclamation mark (F<!>) are
		1216	reserved by F<staticperl>. They must only be used as described in this
		1217	section.
		1218
		1219	=over 4
		1220
		1221	=item !
		1222
		1223	All files that typically cannot be loaded from memory (such as dynamic
		1224	objects or shared libraries), but have to reside in the filesystem, are
		1225	prefixed with F<!>. Typically these files get written out to some
		1226	(semi-)temporary directory shortly after program startup, or before being
		1227	used.
		1228
		1229	=item !boot
		1230
		1231	The bootstrap file, if specified during bundling.
		1232
		1233	=item !auto/
		1234
		1235	Shared objects or dlls corresponding to dynamically-linked perl extensions
		1236	are stored with an F<!auto/> prefix.
		1237
		1238	=item !lib/
		1239
		1240	External shared libraries are stored in this directory.
		1241
		1242	=item any letter
		1243
		1244	Any path starting with a letter is a perl library file. For example,
		1245	F<Coro/AIO.pm> corresponds to the file loaded by C<use Coro::AIO>, and
		1246	F<Coro/jit.pl> corresponds to C<require "Coro/jit.pl">.
		1247
		1248	Obviously, module names shouldn't start with any other characters than
		1249	letters :)
		1250
		1251	=back
		1252
		1253	=head3 FUNCTIONS
		1254
		1255	=over 4
		1256
		1257	=item $file = static::find $path
		1258
		1259	Returns the data associated with the given C<$path>
		1260	(e.g. C<Digest/MD5.pm>, C<auto/POSIX/autosplit.ix>).
		1261
		1262	Returns C<undef> if the file isn't embedded.
		1263
		1264	=item @paths = static::list
		1265
		1266	Returns the list of all paths embedded in this binary.
		1267
		1268	=back
		1269
		1270	=head2 EXTRA FEATURES
1149		1271
1150	In addition, for the embedded loading of perl files to work, F<staticperl>	1272	In addition, for the embedded loading of perl files to work, F<staticperl>
1151	overrides the C<@INC> array.	1273	overrides the C<@INC> array.
1152		1274
1153	=over 4	1275	=head1 FULLY STATIC BINARIES - ALPINE LINUX
1154		1276
1155	=item $file = staticperl::find $path	1277	This section once contained a way to build fully static (including
		1278	uClibc) binaries with buildroot. Unfortunately, buildroot no longer
		1279	supports a compiler, so I recommend using alpine linux instead
		1280	(L<http://alpinelinux.org/>). Get yourself a VM (e.g. with qemu), run an
		1281	older alpine linux verison in it (e.g. 2.4), copy staticperl inside and
		1282	use it.
1156		1283
1157	Returns the data associated with the given C<$path>	1284	The reason you might want an older alpine linux is that uClibc can be
1158	(e.g. C<Digest/MD5.pm>, C<auto/POSIX/autosplit.ix>), which is basically	1285	quite dependent on kernel versions, so the newest version of alpine linux
1159	the UNIX path relative to the perl library directory.	1286	might need a newer kernel then you might want for, if you plan to run your
1160		1287	binaries on on other kernels.
1161	Returns C<undef> if the file isn't embedded.
1162
1163	=item @paths = staticperl::list
1164
1165	Returns the list of all paths embedded in this binary.
1166
1167	=back
1168
1169	=head1 FULLY STATIC BINARIES - UCLIBC AND BUILDROOT
1170
1171	To make truly static (Linux-) libraries, you might want to have a look at
1172	buildroot (L<http://buildroot.uclibc.org/>).
1173
1174	Buildroot is primarily meant to set up a cross-compile environment (which
1175	is not so useful as perl doesn't quite like cross compiles), but it can also compile
1176	a chroot environment where you can use F<staticperl>.
1177
1178	To do so, download buildroot, and enable "Build options => development
1179	files in target filesystem" and optionally "Build options => gcc
1180	optimization level (optimize for size)". At the time of writing, I had
1181	good experiences with GCC 4.4.x but not GCC 4.5.
1182
1183	To minimise code size, I used C<-pipe -ffunction-sections -fdata-sections
1184	-finline-limit=8 -fno-builtin-strlen -mtune=i386>. The C<-mtune=i386>
1185	doesn't decrease codesize much, but it makes the file much more
1186	compressible (and the execution a lot slower...).
1187
1188	If you don't need Coro or threads, you can go with "linuxthreads.old" (or
1189	no thread support). For Coro, it is highly recommended to switch to a
1190	uClibc newer than 0.9.31 (at the time of this writing, I used the 20101201
1191	snapshot) and enable NPTL, otherwise Coro needs to be configured with the
1192	ultra-slow pthreads backend to work around linuxthreads bugs (it also uses
1193	twice the address space needed for stacks).
1194
1195	If you use C<linuxthreads.old>, then you should also be aware that
1196	uClibc shares C<errno> between all threads when statically linking. See
1197	L<http://lists.uclibc.org/pipermail/uclibc/2010-June/044157.html> for a
1198	workaround (and L<https://bugs.uclibc.org/2089> for discussion).
1199
1200	C<ccache> support is also recommended, especially if you want
1201	to play around with buildroot options. Enabling the C<miniperl>
1202	package will probably enable all options required for a successful
1203	perl build. F<staticperl> itself additionally needs either C<wget>
1204	(recommended, for CPAN) or C<curl>.
1205
1206	As for shells, busybox should provide all that is needed, but the default
1207	busybox configuration doesn't include F<comm> which is needed by perl -
1208	either make a custom busybox config, or compile coreutils.
1209
1210	For the latter route, you might find that bash has some bugs that keep
1211	it from working properly in a chroot - either use dash (and link it to
1212	F</bin/sh> inside the chroot) or link busybox to F</bin/sh>, using it's
1213	built-in ash shell.
1214
1215	Finally, you need F</dev/null> inside the chroot for many scripts to work
1216	- either F<cp /dev/null output/target/dev> or bind-mounting your F</dev>
1217	will provide this.
1218
1219	After you have compiled and set up your buildroot target, you can copy
1220	F<staticperl> from the C<App::Staticperl> distribution or from your
1221	perl F<bin> directory (if you installed it) into the F<output/target>
1222	filesystem, chroot inside and run it.
1223		1288
1224	=head1 RECIPES / SPECIFIC MODULES	1289	=head1 RECIPES / SPECIFIC MODULES
1225		1290
1226	This section contains some common(?) recipes and information about	1291	This section contains some common(?) recipes and information about
1227	problems with some common modules or perl constructs that require extra	1292	problems with some common modules or perl constructs that require extra
…		…
1241		1306
1242	Many Unicode properties in turn are defined in separate modules,	1307	Many Unicode properties in turn are defined in separate modules,
1243	such as C<"unicore/Heavy.pl"> and more specific data tables such as	1308	such as C<"unicore/Heavy.pl"> and more specific data tables such as
1244	C<"unicore/To/Digit.pl"> or C<"unicore/lib/Perl/Word.pl">. These tables	1309	C<"unicore/To/Digit.pl"> or C<"unicore/lib/Perl/Word.pl">. These tables
1245	are big (7MB uncompressed, although F<staticperl> contains special	1310	are big (7MB uncompressed, although F<staticperl> contains special
1246	handling for those files), so including them on demand by your application	1311	handling for those files), so including them only on demand in your
1247	only might pay off.	1312	application might pay off.
1248		1313
1249	To simply include the whole unicode database, use:	1314	To simply include the whole unicode database, use:
1250		1315
1251	--incglob '/unicore/**.pl'	1316	--incglob '/unicore/**.pl'
1252		1317
…		…
1289	C<MAN3PODS> to be empty via the C<PERL_MM_OPT> environment variable.	1354	C<MAN3PODS> to be empty via the C<PERL_MM_OPT> environment variable.
1290		1355
1291	=item Gtk2	1356	=item Gtk2
1292		1357
1293	See Pango, same problems, same solution.	1358	See Pango, same problems, same solution.
		1359
		1360	=item Net::SSLeay
		1361
		1362	This module hasn't been significantly updated since OpenSSL is called
		1363	OpenSSL, and fails to properly link against dependent libraries, most
		1364	commonly, it forgets to specify -ldl when linking.
		1365
		1366	On GNU/Linux systems this usually goes undetected, as perl usually links
		1367	against -ldl itself and OpenSSL just happens to pick it up that way, by
		1368	chance.
		1369
		1370	For static builds, you either have to configure -ldl manually, or you
		1371	cna use the following snippet in your C<postinstall> hook which patches
		1372	Net::SSLeay after installation, which happens to work most of the time:
		1373
		1374	postinstall() {
		1375	# first install it
		1376	instcpan Net::SSLeay
		1377	# then add -ldl for future linking
		1378	chmod u+w "$PERL_PREFIX"/lib/auto/Net/SSLeay/extralibs.ld
		1379	echo " -ldl" >>"$PERL_PREFIX"/lib/auto/Net/SSLeay/extralibs.ld
		1380	}
1294		1381
1295	=item Pango	1382	=item Pango
1296		1383
1297	In addition to the C<MAN3PODS> problem in Glib, Pango also routes around	1384	In addition to the C<MAN3PODS> problem in Glib, Pango also routes around
1298	L<ExtUtils::MakeMaker> by compiling its files on its own. F<staticperl>	1385	L<ExtUtils::MakeMaker> by compiling its files on its own. F<staticperl>
…		…
1366	gains little. Why Socket exposes a C function that is in the core already	1453	gains little. Why Socket exposes a C function that is in the core already
1367	is anybody's guess.	1454	is anybody's guess.
1368		1455
1369	=back	1456	=back
1370		1457
		1458	=head1 ADDITIONAL RESOURCES
		1459
		1460	Some guy has made a repository on github
		1461	(L<https://github.com/gh0stwizard/staticperl-modules>) with some modules
		1462	patched to build with staticperl.
		1463
1371	=head1 AUTHOR	1464	=head1 AUTHOR
1372		1465
1373	Marc Lehmann <schmorp@schmorp.de>	1466	Marc Lehmann <schmorp@schmorp.de>
1374	http://software.schmorp.de/pkg/staticperl.html	1467	http://software.schmorp.de/pkg/staticperl.html
		1468

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines

Comparing App-Staticperl/staticperl.pod (file contents): Revision 1.47 by root, Sat Jul 9 18:26:27 2011 UTC vs. Revision 1.66 by root, Fri Aug 4 03:14:33 2023 UTC

Diff Legend

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.47 by root, Sat Jul 9 18:26:27 2011 UTC vs.
Revision 1.66 by root, Fri Aug 4 03:14:33 2023 UTC