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

Dmitry Chestnykh 225478e84d aarch64: Apply relocations to use TLS GD access model. 6 ヶ月 前
docs 0f2cede0fa Added some documentation on how to add static-pie support to the porting guide 2 年 前
extra 672afe85c2 Add vDSO support for aarch64. 6 ヶ月 前
include 0694e42c9c tree: Remove ^L 6 ヶ月 前
ldso 225478e84d aarch64: Apply relocations to use TLS GD access model. 6 ヶ月 前
libc 3a36a3100a Fix vDSO support for all supported architectures. 6 ヶ月 前
libcrypt a908621a93 Replace null subtraction with cast 8 ヶ月 前
libiconv 294e120706 libiconv: add missing header files from previuos commit 6 年 前
libintl e5739032a8 Fix warning due to relaxed function declaration prototype 4 年 前
libm 4ce2bd0e57 libm: fix nexttoward failures, fixed by sorear 7 ヶ月 前
libpthread 0694e42c9c tree: Remove ^L 6 ヶ月 前
librt 3a36a3100a Fix vDSO support for all supported architectures. 6 ヶ月 前
libuargp f93b43e4d1 Fix compilation issue when libuargp is compiled without __UCLIBC_HAS_PROGRAM_INVOCATION_NAME__ 5 年 前
libubacktrace 29ff9055c8 use a single libc and deduplicate threading code 8 年 前
libutil 52df983934 remove editor hints for vi 7 年 前
utils de6be7bc60 arc: add support for ARCv3 32-bit processors 2 年 前
.gitignore cdb07d2cd5 gitignore 1 年間 前
COPYING.LIB 0694e42c9c tree: Remove ^L 6 ヶ月 前
COPYING.LIB.boilerplate 99eb65208a boilerplate license we use 18 年 前
INSTALL b15e3a2d34 INSTALL: add some notes how to create Linux headers directory 6 年 前
MAINTAINERS 08f6c1f1a0 update MAINTAINERS 8 ヶ月 前
Makefile 105ceb0fdc always define CONFIG_SHELL 15 年 前
Makefile.help 99ef2719fb test: remove test suite 8 年 前
Makefile.in df81bd1e2c getauxval: remove header for static builds 1 年間 前
Makerules ed6a951315 Add extra `-shared` to link.so command. 8 ヶ月 前
README 672a303852 kvx: add support for kvx arch to uClibc-ng 4 年 前
Rules.mak 318858b473 bump version for 1.0.47 release 7 ヶ月 前

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, KVX, LM32, M68K/Coldfire, Metag, Microblaze, MIPS, MIPS64, NDS32, NIOS2,
OpenRisc, PowerPC, SuperH, Sparc, Tile, 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