BuildChroot
Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2010-07-07 14:23:10
119
Comment:
|
226
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
=== Get the automated chroot build scripts === | == Get the automated chroot build scripts === |
Line 3: | Line 3: |
== Create the chroot environment == <<Include(Kernel/Action/Scriptbuildmkschroot, ,from="^== .* ==$")>> |
== Get the automated chroot build scripts ===
A common set of tools used by the kernel team are maintained in a git repository.
- buildscripts: Scripts used to farm out the kernel builds to very fast remote
- chroot-setup: Scripts to setup jailed kernel compilation enviroments.
- daily-test-isos: Scripts and support files to produce daily, custom test isos.
- git-hooks: Optional hooks to help you commit patches
- maintscripts: Scripts used for general / stable kernel maintenance
- mainline-build: Scripts to produce .debs for mainline kernels
- misc: Everything else...
Download them using the following command.
git clone git://kernel.ubuntu.com/ubuntu/kteam-tools.git kteam-tools
Create the chroot environment
To automatically create the chroot environment use:
chroot-setup/build-mkschroot [--arch=<arch>] <suite> <target-dir> [<mirror>]
For example:
sudo chroot-setup/build-mkschroot --arch=i386 hardy hardy-i386 http://archive.ubuntu.com/ubuntu
Where:
- arch stands for different arch supported by the CPU, for example i386 on AMD64 or LPIA on i386 etc.
- suite stands for release name such as hardy, gutsy, intrepid etc.
- target-dir stands for the directory where the chroot environment will be installed.
mirror stands for the http location to download environment from, http://host[:port]/dir/
Note: You don't need to specify a mirror when using the LPIA arch
Kernel/Action/BuildChroot (last edited 2012-05-23 15:15:45 by c-24-147-74-79)