From a7c3e292bc48e5faee5731bad0722e037bcc98b0 Mon Sep 17 00:00:00 2001 From: Rob Landley Date: Wed, 1 Jan 2014 13:24:03 -0600 Subject: The README trailed off into unfinished confusion at the end, fix up the obvious parts. --- README | 17 +++++++---------- 1 file changed, 7 insertions(+), 10 deletions(-) diff --git a/README b/README index 4fc2472c..a54e54d9 100644 --- a/README +++ b/README @@ -71,18 +71,15 @@ a program for the system to run (toybox), and a C library to tie them together (toybox has been tested with musl, uClibc, and glibc, on Android systems musl is recommended).

-

The C library is part of a "toolchain", which is an integrated suite +The C library is part of a "toolchain", which is an integrated suite of compiler, assembler, and linker, plus the standard headers and libraries -necessary to build C programs.

+necessary to build C programs. - - Static linking (with the --static option) -copies the shared library contents into the program, resulting in -larger but more portable programs. Dynamically linked programs (the default) -Otherwise, the -"dynamically" linked programs require the -library to be present on the target system ("man ldd" and "man ld.so" for -details) statically linked programs do not.

+Static linking (with the --static option) copies the shared library contents +into the program, resulting in larger but more portable programs, which +can run even if they'rr the only file in the filesystem. Otherwise, +the "dynamically" linked programs require the library files to be present on +the target system ("man ldd" and "man ld.so" for details). Toybox is not a kernel, it needs Linux to drive the hardware. -- cgit v1.2.3