|
@@ -39,7 +39,7 @@
|
|
|
|
|
|
|
|
<a href="http://www.uclibc.org">uClibc</a> (aka µClibc/pronounced
|
|
<a href="http://www.uclibc.org">uClibc</a> (aka µClibc/pronounced
|
|
|
yew-see-lib-see) is a C library for developing embedded Linux systems.
|
|
yew-see-lib-see) is a C library for developing embedded Linux systems.
|
|
|
-It is much smaller then the
|
|
|
|
|
|
|
+It is much smaller than the
|
|
|
<a href="http://www.gnu.org/software/libc/libc.html">GNU C Library</a>,
|
|
<a href="http://www.gnu.org/software/libc/libc.html">GNU C Library</a>,
|
|
|
but nearly all applications supported by glibc also work perfectly with
|
|
but nearly all applications supported by glibc also work perfectly with
|
|
|
uClibc. Porting applications from glibc to uClibc typically involves
|
|
uClibc. Porting applications from glibc to uClibc typically involves
|
|
@@ -52,7 +52,7 @@ PowerPC, SH, SPARC, and v850 processors.
|
|
|
|
|
|
|
|
If you are building an embedded Linux system and you find that glibc is
|
|
If you are building an embedded Linux system and you find that glibc is
|
|
|
eating up too much space, you should consider using uClibc. If you are
|
|
eating up too much space, you should consider using uClibc. If you are
|
|
|
-building a huge fileserver with 12 Terabytes of storage, then using
|
|
|
|
|
|
|
+building a huge fileserver with 12 Terabytes of storage, than using
|
|
|
glibc may be a better choice...
|
|
glibc may be a better choice...
|
|
|
<p>
|
|
<p>
|
|
|
|
|
|
Eric Andersen