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, i386, i960, h8300, 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, than using
glibc may be a better choice...
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
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.
Mailing List Information
uClibc has a mailing list.
To subscribe, go and visit
this page.
Frequently Asked Questions
Before asking questions on the uClibc mailing list,
you might want to take a look at the
list of Frequently Asked Questions
or
you might want to search the mailing list archives...
Working Applications List
These days, pretty much everything compiles with uClibc. This
is a list of applications that are known
to work just fine with uClibc. Since most applications work just
fine with uClibc, we are especially interested in knowing about any
applications that either do not compile or do not work
properly with uClibc. Submissions are welcome!
|
- 30 June 2003, uClibc 0.9.20 Released
CodePoet Consulting is pleased to announce the immediate availability of
uClibc 0.9.20. This is primarily a bug-fix release. This release remains
binary compatible with 0.9.18 and 0.9.19 (as long as you leave the
new UCLIBC_HAS_TM_EXTENSIONS option disabled), so you don't have to recompile
everything if you don't really feel like it.
This release has many small improvements. At this point, most applications
that compile and work with glibc will also compile and run with uClibc.
Perl and Python even pass all the tests in their test suites.
There is currently one notable exception. Applications with use dlopen()
to load libraries that themselves depend on other libraries, may have weak
symbols within those depended-upon libraries resolved incorrectly. This
problem is currently being worked on. Other than that, everything seems to
be working. And everything seems to now be working as expected....
As usual, the
Changelog,
detailed changelog,
and source code for this release
are available here.
- 30 June March 2003, dev systems updated to uClibc 0.9.20
The uClibc development systems for
i386,
powerpc,
arm,
mips,
have been updated to uClibc 0.9.20. Several problems have been fixed up,
gcc has been updated to version 3.3, and Perl 5.8.0 is now included.
This is a 150 MB ext2 filesystem that runs natively on the specified
architecture. It contains all the development software you need to build
your own uClibc applications, including bash, coreutils, findutils,
diffutils, patch, sed, ed, flex, bison, file, gawk, tar, grep gdb, strace,
make, gcc, g++, autoconf, automake, ncurses, zlib, openssl, openssh perl,
and more. And of course, everything is dynamically linked against uClibc. By
using a uClibc only system, you can avoid all the painful
cross-configuration problems that have made using uClibc somewhat painful
in the past. If you want to quickly get started with testing or using
uClibc you should give these images a try. You can loop mount and then
chroot into them, you can boot into them using user-mode Linux, and you can
even 'dd' them to a spare partition and use resize2fs to make them fill the
drive. Whatever works for you.
If you would like to build your own custom uClibc system, you can
use buildroot, which is
how the uClibc development systems were created.
- 6 March 2003, development system updates
The uClibc development systems for
i386,
powerpc,
arm,
and now for the first time
mips,
have been updated to uClibc 0.9.19. Several smaller problems
have also been fixed up.
This is an ext2 filesystem that runs natively on the specified
architecture. It contains all the development software you need to build
your own uClibc applications, including bash, coreutils, findutils,
diffutils, patch, sed, ed, flex, bison, file, gawk, tar, grep gdb, strace,
make, gcc, g++, autoconf, automake, ncurses, zlib, openssl, openssh and
more. And of course, everything is dynamically linked against uClibc. By
using a uClibc only system, you can avoid all the painful
cross-configuration problems that have made using uClibc somewhat painful
in the past. If you want to quickly get started with testing or using
uClibc you should give these images a try. You can loop mount and
then chroot into them, you can boot into them using user-mode Linux,
you can even 'dd' them to a spare partition and use resize2fs to
make them fill the drive. Whatever works best for you.
Have Fun.
- 3 March 2003, uClibc 0.9.19 Released
CodePoet Consulting is pleased to announce the immediate availability of
uClibc 0.9.19. This is once again primarily a bug-fix release. Several
critical problems with system calls were fixed, the pthreads library was
improved, debugging of applications using uClibc's pthreads library is
now possible (requires gdb 5.3 or newer that is compiled using uClibc),
and a number of other random fixes are included. This release retains
binary compatibility with uClibc 0.9.18 (except for mips, which didn't
work properly with uClibc 0.9.18 anyways). Updated development system
images compiled with uClibc 0.9.19 will be released shortly.
As usual, the
Changelog and source code for this release
are available here.
- Old News
Click here to read older news.
|