Bering-uClibc 5.x - Developer Guide - Preparing the Build Environment

From bering-uClibc
Jump to: navigation, search
Preparing the Build Environment
Prev Bering-uClibc 5.x - Developer Guide Next


Pre-Requisites

Hardware

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) for i486 architecture are:

- approx. 3,5 hours with an AMD Athlon(tm) II X4 645 Processor (Quad Core) with 8GB DDR2 RAM, Kubuntu (64-bit)

Add about the same amount of time for other architectures.

Disk Space

A fully built development environment with all of the Bering-uClibc 5.x Packages and all of the kernel variants occupies more than 30 Gigabytes of disk space.

The following statistics were reported on 2012-04-01 but note that the space requirements will gradually grow as more Packages are added:

  • For cloning the Git repository: 1.9GB
  • For building the default Toolchain a further: 3.6GB
  • For building all the Packages for the default Toolchain a further: 5.5GB
  • For building all the Images for the default Toolchain a further: 0.5GB

In total that is approximately 11.5GB.

For planning purposes assume that 15 Gigabytes are required. If building multiple Toolchains then allow an extra 10 Gigabytes for each additional Toolchain.

Operating System

The Bering-uClibc 5.x 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)
  • Fedora 15 (64-bit)
  • Fedora 17 (64-bit)
  • (K)ubuntu 14.04 (64-bit)

Required Software on the Build Host

perl 
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 Perl modules 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:
sudo yum install 'perl(Config::General)' 'perl(Date::Format)' 'perl(parent)' 'perl(List::MoreUtils)' 'perl(Hash::Merge)'
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 liblist-moreutils-perl libhash-merge-perl
git 
LEAF currently uses git for source code version control, so the git utility is required.
patch 
The patch utility is required to apply patches to upstream source distributions.
texinfo 
Required for the makeinfo utility used for some compilation steps, though the resulting .info files are not used.
nasm 
Required to build e3.
zlib-devel (headers for zlib) 
Required to build toolchain (depmod with gzipped modules support).
bison 
Required to build the (TBC) Package.
asciidoc 
Required to build the (TBC) Package.
fakeroot 
Required when building Packages and disk Images, avoiding the need to actually run as the root user on the build host.
cmake 
Required to build accel-ppp
intltool
Required to build avahi
gmp 
Required to build toolchain - including "development" features. On Red Hat systems this normally means installing the RPM for gmp-devel
mpfr 
Required to build toolchain - including "development" features. On Red Hat systems this normally means installing the RPM for mpfr-devel
libmpc 
Required to build toolchain - including "development" features. On Red Hat systems this normally means installing the RPM for libmpc-devel

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:

  • autoconf
  • automake
  • bc
  • binutils (for command strip)
  • bzip2 (for command bzcat)
  • cpio (for generating initrd.lrp)
  • file
  • flex
    • For cross-compiling linux-atm a static version of the build host's flex libfl.a is required. On Red Hat systems this normally means installing the RPM for flex-static.
  • gawk
  • gcc (4.8.x, gcc 5.x does not work yet)
  • gcc-c++
  • gzip (for a gzip-compatible zcat)
  • libtool
    • Including "development" features. On Red Hat systems this normally means installing the RPM for libtool-ltdl-devel.
  • lzma
  • m4
  • make
  • sed
  • tar
  • wget
  • xz
  • lzop

SourceForge User Account

TODO

Cloning the Git Repository

The first step in building Bering-uClibc 5.x from source is 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:

  1. Change to the directory where you wish to do your Bering-uClibc 5.x development.
  2. Run the following command, replacing USERNAME with your SourceForge username: 
    git clone ssh://USERNAME@git.code.sf.net/p/leaf/bering-uclibc bering-uclibc-master
    Note that this will take some time to run, since it has to download the build toolchain source as well as the source for the Bering-uClibc 5.x Packages.
    • If for some reason you do not want or need the full history of changes since this repository was created it is possible to omit the history by including "--depth 1" in the command arguments.

The arguments to the git glone command are as follows:

  • The string "ssh://USERNAME@git.code.sf.net/p/leaf/bering-uclibc" specifies the name of the Git repository to be cloned (including the access mechanism, ssh)
  • The string "bering-uclibc-master" specifies the name of the local directory to be created, under the current working directory, to hold the clone repository. By default the local directory name would match the name of the repository being cloned (i.e. "bering-uclibc").

Building the Build environment

With the source code for the build toolchain downloaded this now has to be compiled for your build host.

Change directory to the bering-uclibc-next directory created during the clone operation.

Run the following command: 

./buildtool.pl build toolchain

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


Prev Up Next
Retrieved from "http://bering-uclibc.zetam.org/index.php?title=Bering-uClibc_5.x_-_Developer_Guide_-_Preparing_the_Build_Environment&oldid=2588"