Embedded C library http://uclibc-ng.org

Eric Andersen 2a01fa1548 Joakim Tjernlund writes: 21 years ago
debian 2fd364618a Update version 21 years ago
docs a48d269eda Add some basic cvs usage info 21 years ago
extra 45e9d9fef0 George Thanos writes: 21 years ago
include 733eb3f9b3 Add some missing prototypes 21 years ago
ldso 2a01fa1548 Joakim Tjernlund writes: 21 years ago
libc b36d61d33e Fix up several errors related to filename length and errno that 21 years ago
libcrypt 36be007b26 Minor cleanup 21 years ago
libintl fe6015e8aa minor cleanup 21 years ago
libm fe6015e8aa minor cleanup 21 years ago
libnsl fe6015e8aa minor cleanup 21 years ago
libpthread dfc535be8f Arthur Shipkowski, art ! videon-central ! com, writes: 21 years ago
libresolv fe6015e8aa minor cleanup 21 years ago
libutil fe6015e8aa minor cleanup 21 years ago
test dae4f33e48 Additional passwd and group tests 21 years ago
utils de6fee730d Sigh. I forgot to define INSTALL which, understandable, 21 years ago
.cvsignore 6737908f74 Ok, this commit is _huge_ and its gonna change the world. I've 22 years ago
COPYING.LIB 64bc641218 Initial revision 24 years ago
Changelog 6a402bb07f minor spelling fixes 21 years ago
Changelog.full 9fe5415568 Update changelog for release 21 years ago
INSTALL fc71b53fcc Fix typo noticed by V.Radhakrishnan 22 years ago
Makefile c8fb354eff remove some junk I added while debugging 21 years ago
README 83d06c569c Yet more trivial doc updates 21 years ago
Rules.mak f0de7b236e It is remotely possible the utils might even compile this time 21 years ago
TODO 6e80c6c0ea Remove some stuff that is now done 21 years ago

README


uClibc - a Small C Library for Linux
Erik Andersen

uClibc (aka Clibc/pronounced yew-see-lib-see) is a C library for
developing embedded Linux systems. It is much smaller than the
GNU C Library, but nearly all applications supported by glibc
also work perfectly with uClibc. Porting applications from glibc
to uClibc typically involves just recompiling the source code.
uClibc even supports shared libraries and threading. It currently
runs on standard Linux and MMU-less (also known as Clinux)
systems with support for alpha, ARM, cris, h8300, i386, i960,
m68k, mips/mipsel, PowerPC, SH, SPARC, and v850 processors.

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 building a huge fileserver with 12 Terabytes
of storage, then using glibc may make more sense. Unless, for
example, that 12 Terabytes will be Network Attached Storage and
you plan to burn Linux into the system's firmware...

uClibc is maintained by Erik Andersen and is licensed under the
GNU LIBRARY GENERAL PUBLIC LICENSE . This license allows you to
make closed source commercial applications using an unmodified
version of uClibc (Please consider sharing some of the money you
make ;-). You do not need to give away all your source code just
because you use uClibc and/or run on Linux.


For installation instructions, see the file INSTALL.

This distribution contains a wrapper for gcc and ld that allows
you to use existing toolchains that were targetted for glibc.
There are limits as to what this wrapper can do, so it is
recommended that you instead build a full binutils/gcc toolchain.

uClibc strives to be standards compliant, which means that most
documentation written for SuSv3, or for glibc also applies to
uClibc functions. However, many GNU extensions are not supported
because they have not been ported, or more importantly, would
increase the size of uClibc disproportional to the added
functionality.

Additional information (recent releases, FAQ, mailing list, bugs,
etc.) can be found at http://www.uclibc.org/.

uClibc may be freely modified distributed under the terms of the
GNU Library General Public License, which can be found in the
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 compatible 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
are especially chummy with glibc, and may need this
behavior disabled by adding CFLAGS+=-D__FORCE_NOGLIBC