7.4. Busybox-1.1.0

BusyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides replacements for most of the utilities you usually find in GNU fileutils, shellutils, etc. The utilities in BusyBox generally have fewer options than their full-featured GNU cousins; however, the options that are included provide the expected functionality and behave very much like their GNU counterparts. BusyBox provides a fairly complete environment for any small or embedded system.

7.4.1. Installation of Busybox

The following patch contains a number of updates to the 1.1.0 branch by the Busybox developers:

patch -Np1 -i ../busybox-1.1.0-branch_update-1.patch

Copy the Busybox config file from where you downloaded it::

cp ${CLFS}/sources/busybox-1.1.0.config .config
[Note]

Note

Below we are just telling Busybox to use the default configuration of Busybox. For those for more adventureous, you can use make menuconfig, and do a more custom build of your Busybox.

Now we will take our configuration we just created, and make Busybox use it:

make oldconfig

Compile the package:

make ARCH=${CLFS_ARCH} CC="${CC} ${BUILD}" CROSS_COMPILE="${CLFS_TARGET}-"

Install the package:

make ARCH=${CLFS_ARCH} CC="${CC} ${BUILD}" CROSS_COMPILE="${CLFS_TARGET}-" \
  CONFIG_PREFIX=${CLFS} install

If your going to build your kernel with modules, you will need to make sure depmod.pl is available:

cp examples/depmod.pl /cross-tools/bin
chmod 755 /cross-tools/bin/depmod.pl

7.4.2. Contents of Busybox

Installed programs: To be Written