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

Waldemar Brodkorb 8fba8eb918 bump for release 1.0.29 6 years ago
docs dc7ad97385 docs: cleanup directory, fix some porting information 7 years ago
extra f20179d693 remove arc4random (rc4 based) 6 years ago
include cef9840613 fix issue with LDSO_GNU_HASH_SUPPORT 6 years ago
ldso 7cc754bc93 bits/mman.h: consolidate header file 6 years ago
libc 7bb52872a7 add missing include to quieten compiler 6 years ago
libcrypt 52df983934 remove editor hints for vi 7 years ago
libiconv 6018c3787a libiconv: fake EUC_JP support 6 years ago
libintl b39b5151b9 add stub implementation for libintl/gettext 8 years ago
libm 7ebfbe2940 libm: fix compile error 6 years ago
libpthread 5d5338562e add libc version compatibility 6 years ago
librt 8ff62fe8dc rt: cleanup and allow to build for linuxthreads 6 years ago
libuargp 50aba30aee remove libintl stub and libintl.h header 8 years ago
libubacktrace 29ff9055c8 use a single libc and deduplicate threading code 8 years ago
libutil 52df983934 remove editor hints for vi 7 years ago
utils 0cbf892ff2 utils: fix install error 6 years ago
.gitignore 30c4dd1f3a .gitignore: Ignore dump files 12 years ago
COPYING.LIB 751dd180c3 Update license file to Lesser GPL v2.1 19 years ago
COPYING.LIB.boilerplate 99eb65208a boilerplate license we use 18 years ago
INSTALL b15e3a2d34 INSTALL: add some notes how to create Linux headers directory 7 years ago
MAINTAINERS a3f6c0c836 add Stafford as OpenRisc Maintainer, agreed on IRC 6 years ago
Makefile 105ceb0fdc always define CONFIG_SHELL 15 years ago
Makefile.help 99ef2719fb test: remove test suite 8 years ago
Makefile.in 4d466d8ada remove unused HP_TIMING_AVAIL and header 7 years ago
Makerules b39b5151b9 add stub implementation for libintl/gettext 8 years ago
README 795d6102e9 bump version to 1.0.28 6 years ago
Rules.mak 8fba8eb918 bump for release 1.0.29 6 years ago

README

uClibc-ng - a small C Library for Linux

uClibc-ng (aka µClibc-ng/pronounced yew-see-lib-see-next-generation) 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-ng.

uClibc-ng is a spin-off of uClibc from http://www.uclibc.org from Erik Andersen
and others.

Porting applications from glibc to uClibc-ng typically involves just
recompiling the source code. uClibc-ng even supports shared libraries and
threading. It currently runs on standard Linux and MMU-less (also known as
µClinux) systems with support for Alpha, ARC, ARM, Blackfin, CRIS, FR-V, HPPA,
IA64, LM32, M68K/Coldfire, Metag, Microblaze, MIPS, MIPS64, NDS32, NIOS2,
OpenRisc, PowerPC, SuperH, Sparc, x86, x86_64 and Xtensa 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-ng. 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-ng is maintained by Waldemar Brodkorb and is licensed under the GNU
LESSER GENERAL PUBLIC LICENSE. This license allows you to make closed source
commercial applications using an unmodified version of uClibc-ng. You do not
need to give away all your source code just because you use uClibc-ng and/or
run on Linux. You should, however, carefuly review the license and make certain
you understand and abide by it strictly.

For installation instructions, see the file INSTALL.

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

Additional information can be found at https://uclibc-ng.org/.

uClibc-ng may be freely modified and distributed under the terms of the GNU
Lesser General Public License, which can be found in the file COPYING.LIB.

And most of all, be sure to have some fun! :-)
-Waldemar