### Toolchains

To use uClibc, you need to have a toolchain, which is composed of binutils, gcc, and of course uClibc.

- You can build your own uClibc toolchain using this to automagically download all the needed source code and compile everything for you.

- Steven J. Hill has kindly provided RPMs and SRPMs with toolchains for mips.

- You can compile your own uClibc development system using buildroot.

- Prebuilt uClibc development systems for i386 and arm and mipsel are available and contain complete native gcc 3.3.2 toolchains. These are development systems are ext2 filesystems that runs natively on the specified architecture. They contain 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 them 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, and then boot into them. Whatever works for you.