--- App-Staticperl/staticperl.pod	2013/06/16 04:38:38	1.58
+++ App-Staticperl/staticperl.pod	2015/07/06 23:33:15	1.59
@@ -1231,60 +1231,19 @@
 In addition, for the embedded loading of perl files to work, F<staticperl>
 overrides the C<@INC> array.
 
-=head1 FULLY STATIC BINARIES - UCLIBC AND BUILDROOT
+=head1 FULLY STATIC BINARIES - ALPINE LINUX
 
-To make truly static (Linux-) libraries, you might want to have a look at
-buildroot (L<http://buildroot.uclibc.org/>).
-
-Buildroot is primarily meant to set up a cross-compile environment (which
-is not so useful as perl doesn't quite like cross compiles), but it can also compile
-a chroot environment where you can use F<staticperl>.
-
-To do so, download buildroot, and enable "Build options => development
-files in target filesystem" and optionally "Build options => gcc
-optimization level (optimize for size)". At the time of writing, I had
-good experiences with GCC 4.4.x but not GCC 4.5.
-
-To minimise code size, I used C<-pipe -ffunction-sections -fdata-sections
--finline-limit=8 -fno-builtin-strlen -mtune=i386>. The C<-mtune=i386>
-doesn't decrease codesize much, but it makes the file much more
-compressible (and the execution a lot slower...).
-
-If you don't need Coro or threads, you can go with "linuxthreads.old" (or
-no thread support). For Coro, it is highly recommended to switch to a
-uClibc newer than 0.9.31 (at the time of this writing, I used the 20101201
-snapshot) and enable NPTL, otherwise Coro needs to be configured with the
-ultra-slow pthreads backend to work around linuxthreads bugs (it also uses
-twice the address space needed for stacks).
-
-If you use C<linuxthreads.old>, then you should also be aware that
-uClibc shares C<errno> between all threads when statically linking. See
-L<http://lists.uclibc.org/pipermail/uclibc/2010-June/044157.html> for a
-workaround (and L<https://bugs.uclibc.org/2089> for discussion).
-
-C<ccache> support is also recommended, especially if you want
-to play around with buildroot options. Enabling the C<miniperl>
-package will probably enable all options required for a successful
-perl build. F<staticperl> itself additionally needs either C<wget>
-(recommended, for CPAN) or C<curl>.
-
-As for shells, busybox should provide all that is needed, but the default
-busybox configuration doesn't include F<comm> which is needed by perl -
-either make a custom busybox config, or compile coreutils.
-
-For the latter route, you might find that bash has some bugs that keep
-it from working properly in a chroot - either use dash (and link it to
-F</bin/sh> inside the chroot) or link busybox to F</bin/sh>, using it's
-built-in ash shell.
-
-Finally, you need F</dev/null> inside the chroot for many scripts to work
-- either F<cp /dev/null output/target/dev> or bind-mounting your F</dev>
-will provide this.
-
-After you have compiled and set up your buildroot target, you can copy
-F<staticperl> from the C<App::Staticperl> distribution or from your
-perl F<bin> directory (if you installed it) into the F<output/target>
-filesystem, chroot inside and run it.
+This section once contained a way to build fully static (including
+uClibc) binaries with buildroot. Unfortunately, buildroot no longer
+supports a compiler, so I recommend using alpine linux instead
+(L<http://alpinelinux.org/>). Get yourself a VM (e.g. with qemu), run an
+older alpine linux verison in it (e.g. 2.4), copy staticperl inside and
+use it.
+
+The reason you might want an older alpine linux is that uClibc can be
+quite dependent on kernel versions, so the newest version of alpine linux
+might need a newer kernel then you might want for, if you plan to run your
+binaries on on other kernels.
 
 =head1 RECIPES / SPECIFIC MODULES
 
@@ -1455,7 +1414,14 @@
 
 =back
 
+=head1 ADDITIONAL RESOURCES
+
+Some guy has made a repository on github
+(L<https://github.com/gh0stwizard/staticperl-modules>) with some modules
+patched to build with staticperl.
+
 =head1 AUTHOR
 
  Marc Lehmann <schmorp@schmorp.de>
  http://software.schmorp.de/pkg/staticperl.html
+