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

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.49 by root, Wed Jul 13 15:23:13 2011 UTC vs.
Revision 1.57 by root, Wed Dec 5 15:19:52 2012 UTC

 =head1 NAME
-staticperl - perl, libc, 100 modules, all in one 500kb file
+staticperl - perl, libc, 100 modules, all in one standalone 500kb file
 =head1 SYNOPSIS
    staticperl help      # print the embedded documentation
    staticperl fetch     # fetch and unpack perl sources
    staticperl install   # build and then install perl
    staticperl clean     # clean most intermediate files (restart at configure)
    staticperl distclean # delete everything installed by this script
    staticperl perl ...  # invoke the perlinterpreter
    staticperl cpan      # invoke CPAN shell
-   staticperl instmod path...        # install unpacked modules
+   staticperl instsrc path...        # install unpacked modules
    staticperl instcpan modulename... # install modules from CPAN
    staticperl mkbundle <bundle-args...> # see documentation
    staticperl mkperl <bundle-args...>   # see documentation
    staticperl mkapp appname <bundle-args...> # see documentation
    add eg/httpd httpd.pm
 All options that specify modules or files to be added are processed in the
 order given on the command line.
-=head3 BUNDLE CREATION WORKFLOW / STATICPELR MKBUNDLE OPTIONS
+=head3 BUNDLE CREATION WORKFLOW / STATICPERL MKBUNDLE OPTIONS
 F<staticperl mkbundle> works by first assembling a list of candidate
 files and modules to include, then filtering them by include/exclude
 patterns. The remaining modules (together with their direct dependencies,
 such as link libraries and L<AutoLoader> files) are then converted into
    # then later, in perl, use
    use myfiles::file1;
    require myfiles::file2;
    my $res = do "myfiles/file3.pl";
-=item C<--binadd> F<file> | C<--add> "F<file> alias"
+=item C<--binadd> F<file> | C<--binadd> "F<file> alias"
 Just like C<--add>, except that it treats the file as binary and adds it
 without any postprocessing (perl files might get stripped to reduce their
 size).
 standalone applications, and this option removes those known to cause
 trouble.
 Specifically, these are removed:
-C<PERL_HASH_SEED_DEBUG> and C<PERL_DEBUG_MSTATS> can cause underaible
+C<PERL_HASH_SEED_DEBUG> and C<PERL_DEBUG_MSTATS> can cause undesirable
 output, C<PERL5OPT>, C<PERL_DESTRUCT_LEVEL>, C<PERL_HASH_SEED> and
 C<PERL_SIGNALS> can alter execution significantly, and C<PERL_UNICODE>,
 C<PERLIO_DEBUG> and C<PERLIO> can affect input and output.
 The variables C<PERL_LIB> and C<PERL5_LIB> are always ignored because the
 - some modules (such as L<Coro> or L<EV>) use environment variables for
 further tweaking.
 =item C<PERL_PREFIX>
-The prefix where perl gets installed (default: F<$STATICPERL/perl>),
+The directory where perl gets installed (default: F<$STATICPERL/perl>),
-i.e. where the F<bin> and F<lib> subdirectories will end up.
+i.e. where the F<bin> and F<lib> subdirectories will end up. Previous
+contents will be removed on installation.
 =item C<PERL_CONFIGURE>
 Additional Configure options - these are simply passed to the perl
 Configure script. For example, if you wanted to enable dynamic loading,
 F<~/.staticperlrc> to override them.
 Most of the variables override (or modify) the corresponding F<Configure>
 variable, except C<PERL_CCFLAGS>, which gets appended.
-You should have a look near the beginning of the F<staticperl> script -
+The default for C<PERL_OPTIMIZE> is C<-Os> (assuming gcc), and for
-staticperl tries to default C<PERL_OPTIMIZE> to some psace-saving options
+C<PERL_LIBS> is C<-lm -lcrypt>, which should be good for most (but not
-suitable for newer gcc versions. For other compilers or older versions you
+all) systems.
+For other compilers or more customised optimisation settings, you need to
-need to adjust these, for example, in your F<~/.staticperlrc>.
+adjust these, e.g. in your F<~/.staticperlrc>.
+With gcc on x86 and amd64, you can get more space-savings by using:
+   -Os -ffunction-sections -fdata-sections -finline-limit=8 -mpush-args
+   -mno-inline-stringops-dynamically -mno-align-stringops
+And on x86 and pentium3 and newer (basically everything you might ever
+want to run on), adding these is even better for space-savings (use
+-mtune=core2 or something newer for much faster code, too):
+   -fomit-frame-pointer -march=pentium3 -mtune=i386
 =back
 =head4 Variables you probably I<do not want> to override
 C<MAN3PODS> to be empty via the C<PERL_MM_OPT> environment variable.
 =item Gtk2
 See Pango, same problems, same solution.
+=item Net::SSLeay
+This module hasn't been significantly updated since OpenSSL is called
+OpenSSL, and fails to properly link against dependent libraries, most
+commonly, it forgets to specify -ldl when linking.
+On GNU/Linux systems this usually goes undetected, as perl usually links
+against -ldl itself and OpenSSL just happens to pick it up that way, by
+chance.
+For static builds, you either have to configure -ldl manually, or you
+cna use the following snippet in your C<postinstall> hook which patches
+Net::SSLeay after installation, which happens to work most of the time:
+   postinstall() {
+      # first install it
+      instcpan Net::SSLeay
+      # then add -ldl for future linking
+      chmod u+w "$PERL_PREFIX"/lib/auto/Net/SSLeay/extralibs.ld
+      echo " -ldl" >>"$PERL_PREFIX"/lib/auto/Net/SSLeay/extralibs.ld
+   }
 =item Pango
 In addition to the C<MAN3PODS> problem in Glib, Pango also routes around
 L<ExtUtils::MakeMaker> by compiling its files on its own. F<staticperl>

Diff Legend

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

Comparing App-Staticperl/staticperl.pod (file contents): Revision 1.49 by root, Wed Jul 13 15:23:13 2011 UTC vs. Revision 1.57 by root, Wed Dec 5 15:19:52 2012 UTC

Diff Legend

Comparing App-Staticperl/staticperl.pod (file contents):
Revision 1.49 by root, Wed Jul 13 15:23:13 2011 UTC vs.
Revision 1.57 by root, Wed Dec 5 15:19:52 2012 UTC