+For architectures with both little- and big-endian options, both are
+supported unless otherwise noted.
+
+In general, musl assumes the availability of all Linux syscall
+interfaces available in Linux 2.6.0. Some programs that do not use
+threads or other modern functionality may be able to run on 2.4.x
+kernels. Other kernels (such as BSD) that provide a Linux-compatible
+syscall ABI should also work but have not been extensively tested.
+
+
+
+==== Option 1: Installing musl as an alternate C library ====
+
+In this setup, musl and any third-party libraries linked to musl will
+reside under an alternate prefix such as /usr/local/musl or /opt/musl.
+A wrapper script for gcc, called musl-gcc, can be used in place of gcc
+to compile and link programs and libraries against musl.
+
+(Note: There are not yet corresponding wrapper scripts for other
+compilers, so if you wish to compile and link against musl using
+another compiler, you are responsible for providing the correct
+options to override the default include and library search paths.)
+
+To install musl as an alternate libc, follow these steps:
+
+1. Configure musl's build with a command similar to:
+ ./configure --prefix=/usr/local/musl --exec-prefix=/usr/local
+ Refer to ./configure --help for details on other options. You may
+ change the install prefix if you like, but DO NOT set it to a
+ location that contains your existing libraries based on another
+ libc such as glibc or uClibc. If you do not intend to use dynamic
+ linking, you may disable it at this point via --disable-shared and
+ cut the build time in half. If you wish to use dynamic linking but
+ do not have permissions to write to /lib, you will need to set an
+ alternate dynamic linker location via --syslibdir.
+
+2. Run "make". Parallel build is fully supported, so you can instead
+ use "make -j3" or so on SMP systems if you like.
+
+3. Run "make install" as a user sufficient privileges to write to the
+ destination.
+
+4. Create a file named /etc/ld-musl-$ARCH.path (where $ARCH is
+ replaced by i386, x86_64, etc. as appropriate) containing the
+ correct colon-delimited search path for where you intend to install
+ musl-linked shared library files. If this file is missing, musl
+ will search the standard path, and you will encounter problems when
+ it attempts to load libraries linked against your host libc. Note
+ that this step can be skipped if you disabled dynamic linking.
+
+After installing, you can use musl via the musl-gcc wrapper. For
+example: