The downloads/binaries directory contains prebuilt binary images, created by running sources/more/buildall.sh in the most recent Aboriginal Linux source tarball. The source packages for these binaries are mirrored at "http://aboriginal.impactlinux.com/mirror". The following tarballs are found here: cross-compiler-$ARCH.tar.bz2 C and C++ Cross compilers, which create target binaries for each architecture, linked against uClibc (and uClibc++ for C++ source). To use, extract this tarball anywhere and add its "bin" subdirectory to your $PATH, then use the appropriate $ARCH-gcc as your target compiler. These are built for an i686 host and statically linked against uClibc, for maximum portability between PC Linux distributions. Includes uClibc++ (to support C++), and thread support. root-filesystem-$ARCH.tar.bz2 Native Linux root filesystem for a given target, suitable for chrooting into (on appropriate hardware) or packaging up into a bootable system image. It contains busybox, uClibc, a simple boot script (usr/sbin/init.sh), and a native toolchain with which to build additional target binaries from source. native-compiler-$ARCH.tar.bz2 Statically linked version of the native compiler from root-filesystem, which you can extract and run on an appropriate target the same way you can extract and run the cross-compiler on the host. You don't need this when using Aboriginal Linux's system images, which provide their own native compiler. This is provided for use with existing target filesystems. system-image-$ARCH.tar.bz2 Prepackaged bootable system images image for each target. The above root-filesystem files packaged into a squashfs image, plus an appropriately configured Linux kernel, and a wrapper script to invoke the emulator QEMU on the two of them. This allows you to compile additional packages natively under QEMU. (Just wget the source tarball at the shell prompt, and build it normally.) The run-emulator.sh wrapper script should produce a shell prompt, with the emulator's stdin/stdout connected to the emulated system's /dev/console. See the screenshots page for examples. The dev-environment.sh script calls run-emulator.sh with a few extra arguments to provide a better development environment (namely a 2 gigabyte writeable ext2 image mounted on /home and 256 megs of memory for the emulated system). If both distccd and the appropriate $ARCH-cc cross compiler are in the $PATH, run-emulator.sh will automatically set up distcc to call out through the virtual network to the host's $ARCH-cc, to move the heavy lifting of compilation outside the emulator, and also take advantage of SMP. (Doing so does not require the package being built to be cross compile aware. As far as the emulated build environment is concerned, it's still performing simple single-context native builds.) rw-system-image-$ARCH Same as system-image-$ARCH, except that the root filesystem image is a writeable ext2 image instead of a read-only squashfs. This takes up more space, and can't be shared between multiple simultaneous emulator instances. The advantage is that additional software can be installed into the root filesystem. This is created with the BUILD_RW_SYSTEM_IMAGE=1 config option. busybox-$ARCH This is a prebuilt static busybox binary for the given target, implementing numerous standard command line utilities. To use, copy it to a target system (perhaps via wget), set the executable bit, and create the appropriate symlinks to it. Run ./busybox-$ARCH to see the list of supported commands. dropbearmulti-$ARCH This is a prebuilt static dropbear binary for the given target, implementing an ssh server and client. To use, copy it to a target system (perhaps via wget), set the executable bit, and create the appropriate symlinks to it. Run ./dropbearmulti-$ARCH to see the list of supporte commands. strace-$ARCH This is a prebuilt static strace binary for the given target, providing a debugging tool listing all the system calls made by another program. To use, copy it to a target system (perhaps via wget) and set the executable bit.