Bering-uClibc 5.x - Developer Guide - Preparing the Build Environment
|Preparing the Build Environment|
|Prev||Bering-uClibc-next - Developer Guide||Next|
CPU & RAM
Compiling source code is a CPU- and RAM-intensive operation, so a reasonably powerful machine is advisable. Multiple CPU cores are a benefit - almost all packages are compiled using all cores.
Examples of build performance for "buildtool.pl build" (unpack and build all packages) are:
- 120 minutes
- AMD Athlon(tm) II X4 645 Processor (Quad Core) with 2GB DDR2 RAM, Gentoo (64-bit)
A fully built development environment with all of the Bering-uClibc 4.x Packages and all of the kernel variants occupies more than 8.1 Gigabytes of disk space.
Assume that 8.5 Gigabytes are required.
The Bering-uClibc-next kernel and Packages can be built on any modern Linux distribution which has the necessary software development utilities installed. Examples of distributions which are known to work include:
- Gentoo (64-bit)
Required Software on the Build Host
- All of the "build" utilities (buildtool, buildpackage, buildimage) are written in Perl and require Perl version 5.6 or higher.
- In addition there is a requirement for the Config::General Perl module which is not part of most standard Perl installations. On distributions which use the "yum" package manager (Red Hat, Fedora etc.) the required RPM can usually be installed with:
yum install perl-Config-General
- Furthermore, the
buildimage.plutility relies on the Date::Format Perl module which is part of the TimeDate Perl package and can be installed with a command like:
yum install perl-TimeDate
- On distributions which use the "dpkg" package manager (Debian, Ubuntu etc.) the required packages can usually be installed with:
aptitude install libconfig-general-perl libdatetime-perl
- LEAF currently uses CVS for source code version control, so the cvs utility is required.
- CVS is now being replaced by Git so the git utility is required as well as / instead of cvs.
- The patch utility is required to apply patches to upstream source distributions.
- There is no longer a requirement to use GCC version 3. GCC version 4 (e.g. 220.127.116.11) works well.
- Note: For Ubuntu 11.11 you'll need to install gcc-multilib
- Required for the makeinfo utility used for some compilation steps, though the resulting .info files are not used.
- Required to build e3.
- zlib-devel (headers for zlib)
- Required to build toolchain (depmod with gzipped modules support).
- Required to build the (TBC) Package.
- Required to build the (TBC) Package.
- Required when building Packages and disk Images, avoiding the need to actually run as the root user on the build host.
- Required to build accel-ppp
In addition, the following RPM or similar packages are also required on the build host but are normally a standard part of the base Linux distribution:
- binutils (for command strip)
- bzip2 (for command bzcat)
- cpio (for generating initrd.lrp)
- gzip (for a gzip-compatible zcat)
SourceForge User Account
Cloning the Git Repository
The first step in building Bering-uClibc-next from source is therefore to copy or "clone" the Git repository hosted by SourceForge. Further information on using Git can be found in Appendix Hints and Tips for using Git SCM but the basic steps are as follows:
- Change to the directory where you wish to do your Bering-uClibc-next development.
- Run the following command, replacing USERNAME with your SourceForge username:
git clone ssh://USERNAME@leaf.git.sourceforge.net/gitroot/leaf/bering-uclibc4 -b next bering-uclibc-nextNote that this will take some time to run, since it has to download the build toolchain source as well as the source for most of the Bering-uClibc-next Packages.
- Change directory to the
vdirectory created during the "clone". This equates to the "repository" name at the end of the Git URL.
Building the Build environment
With the source code for the build toolchain downloaded this now has to be compiled for your build host. Run the following command:
./buildtool.pl build buildenv
This will take some considerable time.
Build messages, including any errors, are written to file
log/buildtoollog so you may wish to run the following command in another shell window to keep track of progress:
tail -f log/buildtoollog