Browse Source

Minor updates.

Eric Andersen 23 years ago
parent
commit
15844e5618
2 changed files with 32 additions and 34 deletions
  1. 0 12
      INSTALL
  2. 32 22
      README

+ 0 - 12
INSTALL

@@ -50,15 +50,3 @@ Note:
 	additional information concerning what options and environment
 	additional information concerning what options and environment
 	variables the gcc wrapper handles.
 	variables the gcc wrapper handles.
 
 
-Note2: 
-
-	There is an unwholesomely huge amount of code out there that
-	depends on the presence of GNU libc header files.  We have GNU
-	libc header files.  So we have committed a horrible sin in
-	uClibc.  We _lie_ and claim to be GNU libc in order to force
-	many applications to work as their developers intended.  This
-	is IMHO, pardonable, since these defines are not really
-	intended to check for the presence of a particular library, but
-	rather are used to define an _interface_.  Some programs (such
-	as GNU binutils) are especially chummy with glibc, and need
-	this behavior disabled by adding CFLAGS+=-D__FORCE_NOGLIBC

+ 32 - 22
README

@@ -1,32 +1,29 @@
 
 
-  uClibc - a small libc implementation
+  uClibc - a Small C Library for Linux
-  Erik Andersen <erik@codepoet.org>
+  Erik Andersen <andersen@codepoet.org>
-
+
-
+uClibc (aka µClibc/pronounced yew-see-lib-see) is a size-optimized
-uClibc (aka µClibc/pronounced yew-see-lib-see) is size-optimized
+implementation of the standard C library.  It is primarily designed
-implementation of the standard C library.  The primary use is
+for developing embedded Linux systems.  It is much smaller then the
-for developing embedded Linux systems.  It is much smaller then
+GNU C Library, but nearly all applications supported by glibc also
-the GNU C Library (glibc), but nearly all applications supported
+work perfectly with uClibc. Porting applications from glibc to
-by glibc also compile and work perfectly with uClibc.  Porting
+uClibc typically involves just recompiling the source code. uClibc
-applications from glibc to uClibc typically involves just
+even supports shared libraries and threading. It currently runs on
-recompiling the source code.  uClibc even supports shared
+standard Linux and MMU-less (also known as µClinuxClinux) systems
-libraries and threading.  It currently runs on standard Linux
+with support for ARM, i386, h8300, m68k, mips, mipsel, PowerPC, SH,
-and MMU-less Linux (also known as µClinux) systems on the
+SPARC, and v850 processors.
-following processors: ARM, i386, h8300, m68k, mips, mipsel,
-PowerPC, SH, SPARC, and v850.
 
 
 For installation instructions, see the file INSTALL.
 For installation instructions, see the file INSTALL.
 
 
-This distribution contains a wrapper for gcc and ld that allows
+This distribution contains a wrapper for gcc and ld that allows you
-you to use existing toolchains that were targetted for glibc.
+to use existing toolchains that were targetted for glibc.  See
-See extra/gcc-uClibc/ for information.
+extra/gcc-uClibc/ for information.
 
 
 uClibc strives to be standards compliant, which means that most
 uClibc strives to be standards compliant, which means that most
 documentation written for functions in glibc also apply to uClibc
 documentation written for functions in glibc also apply to uClibc
-functions.  However, many GNU extensions are not supported
+functions.  However, many GNU extensions are not supported because
-because they have not been ported, or more importantly, would
+they have not been ported, or more importantly, would increase the
-increase the size of uClibc disproportional to the added
+size of uClibc disproportional to the added functionality.
-functionality.
 
 
 Additional information (recent releases, FAQ, mailing list, bugs,
 Additional information (recent releases, FAQ, mailing list, bugs,
 etc.) can be found at http://www.uclibc.org/.
 etc.) can be found at http://www.uclibc.org/.
@@ -35,4 +32,17 @@ uClibc may be freely modified distributed under the terms of the
 GNU Library General Public License, which can be found in the
 GNU Library General Public License, which can be found in the
 file COPYING.LIB.
 file COPYING.LIB.
 
 
+Please Note:
+
+	There is an unwholesomely huge amount of code out there
+	that depends on the presence of GNU libc header files.
+	We have GNU libc header files.  So we have committed a
+	horrible sin in uClibc.  We _lie_ and claim to be GNU
+	libc in order to force these applications to work as their
+	developers intended.  This is IMHO, pardonable, since
+	these defines are not really intended to check for the
+	presence of a particular library, but rather are used to
+	define an _interface_.  Some programs (such as GNU
+	binutils) are especially chummy with glibc, and need this
+	behavior disabled by adding CFLAGS+=__FORCE_NOGLIBC