This release continues to be binary compatible with uClibc 0.9.21 to 0.9.23 -- as long as you pick compatible configuration options. The next release will not be binary compatible. We've been saving up a few needed changes that will be going into the next release, so while you will not need to recompile all your applications and libraries just yet, keep in mind we will have a flag day soon...

As usual, the Changelog, detailed changelog, and source code for this release are available here.

This release continues to be binary compatible with uClibc 0.9.21 and 0.9.22 -- as long as you pick compatible configuration options. Enabling or disabling things like soft-float, locale, wide char support, or changing cpu optimizations are all good examples of binary incompatible configuration options. If have changed any of those sorts of options (or if you are not sure!) you will need to recompile all your applications and libraries.

As usual, the Changelog, detailed changelog, and source code for this release are available here.

This release is binary compatible with uClibc 0.9.21 -- as long as you pick compatible configuration options. Enabling or disabling things like soft-float, locale, wide char support, or changing cpu optimizations are all good examples of binary incompatible configuration options. If have changed any of those sorts of options (or if you are not sure!) you will need to recompile all your applications and libraries.

Updated uClibc development systems using uClibc 0.9.22 will be made available within a few days. Meanwhile, we invite you to try out uClibc with the latest Linux Test Project test suite (you will need to apply a small patch. And also give the latest Perl and Python test suites a try as well. If you find any bugs in uClibc, PLEASE let us know!

As usual, the Changelog, detailed changelog, and source code for this release are available here.

These are ~100 MB ext2 filesystems that run natively on the specified architecture. They 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 them you can chroot into them, you can boot into with 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 these uClibc development systems were created.