ToolchainsTo use uClibc, you need to have a toolchain. A toolchain consists of GNU binutils, the GNU Compiler Collection GCC, and uClibc, all built to produce binaries for your target system linked with uClibc. You can build your own native uClibc toolchain using the uClibc buildroot system.
To build your own uClibc toolchain, follow the following simple steps:
If you want to be really lazy and start using uClibc right away without needing to compile your own toolchain or anything, you can grab a pre-compiled uClibc development system. These are currently available for arm, armeb, i386, mips, mipsel, powerpc, and sh4.
Note: that the images mentioned above are old and ment for demonstration purposes only.
These are bzip2 compressed ext2 filesystems containing all the development software you need to build your own uClibc applications, including: bash, awk, make, gcc, g++, autoconf, automake, ncurses, zlib, openssl, openssh, gdb, strace, busybox, GNU coreutils, GNU tar, GNU grep, etc.
Each of these uClibc development systems was created using buildroot, specifically, buildroot-0.9.27.tar.bz2 along with these sources.
These development systems should provide pretty much everything you need to get started building your own applications with uClibc. Once you download one of these systems, you can then boot into it, loop mount it, dd it to a spare drive and use a tool such as resize2fs to make it fill a partition... Whatever works best for you.
The quickest way to get started using a root_fs image (using the i386 platform as an example) is:
Copyright © 1999-2012 Erik Andersen
Mail all comments, insults, suggestions and bribes to