BuildEABIChroot

Differences between revisions 6 and 12 (spanning 6 versions)
Revision 6 as of 2009-08-17 13:23:13
Size: 2313
Editor: p5098ed03
Comment:
Revision 12 as of 2016-08-17 22:35:01
Size: 2257
Editor: mariogrip
Comment: Update to newer version of arm and update to vivid
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
The binfmt-misc module in the kernel makes it possible to execute binaries of foreign arches under linux.
Qemu can use this fact to enable several architecture specific execution environments in userspace without the need to run a kernel of the target architecture. ARM EABI support is included in the 0.11.x release used in ubuntu karmic today.
The binfmt-misc module in the kernel makes it possible to execute binaries of foreign architectures by using a binary translator such as qemu.
Qemu can run execution environments in userspace without running a kernel of the target architecture (e.g., a virtual machine). Qemu supports several architectures in this way, including ARM.
Line 5: Line 5:
A binary package called qemu-arm-static exists in the karmic universe repository now. it contains such a static binary, automatically enables the binfmt configuration, sets the proper sysctl variables and ships a wrapper script to debootstrap called build-arm-chroot. A binary package called qemu-user-static exists that contains such a static qemu binary, automatically enables the binfmt configuration, sets the proper sysctl variables and ships a wrapper script to debootstrap called qemu-debootstrap.
Line 9: Line 9:
 /!\ Note that the way the qemu userspace emulation is implemented makes it act like a translation layer for syscalls, the syscalls between ARM and x86 systems do not match 1:1 so you still might see some that are not properly translated by the patches (mono packages specifically do not work hre). While the setup below works fine, it should not be trusted for critical work (do not use it to implement a buildd if you plan to rebuild the whole distro for example, its fine for home use to do testbuilds of packages or rolling chroots for creating root filesystems that you want to run on real hardware later on though)  /!\ Note that the way the qemu userspace emulation is implemented makes it act like a translation layer for syscalls, the syscalls between ARM and x86 systems do not match 1:1 so you still might see some that are not properly translated by the patches ('''mono packages specifically do not work here'''). While the setup below works fine, it should not be trusted for critical work (do not use it to implement a buildd if you plan to rebuild the whole distro for example, its fine for home use to do testbuilds of packages or rolling chroots for creating root filesystems that you want to run on real hardware later on though)
Line 13: Line 13:
To use an arm eabi enabled chroot on your i386 system, install the qemu-arm-static package from karmic's universe repository ... To use an arm eabi enabled chroot on your i386 system, install the qemu-user-static package.
Line 17: Line 17:
sudo apt-get install qemu-arm-static sudo apt-get install qemu-user-static
Line 23: Line 23:
ogra@osiris:~$ build-arm-chroot karmic eabi-chroot ogra@osiris:~$ sudo qemu-debootstrap --arch armhf vivid eabi-chroot
Line 34: Line 34:
armv5tel armv7l

The binfmt-misc module in the kernel makes it possible to execute binaries of foreign architectures by using a binary translator such as qemu. Qemu can run execution environments in userspace without running a kernel of the target architecture (e.g., a virtual machine). Qemu supports several architectures in this way, including ARM.

To make use of this feature to build chroots, qemu needs to be build as a static binary. A binary package called qemu-user-static exists that contains such a static qemu binary, automatically enables the binfmt configuration, sets the proper sysctl variables and ships a wrapper script to debootstrap called qemu-debootstrap.


  • Warning /!\ Note that the way the qemu userspace emulation is implemented makes it act like a translation layer for syscalls, the syscalls between ARM and x86 systems do not match 1:1 so you still might see some that are not properly translated by the patches (mono packages specifically do not work here). While the setup below works fine, it should not be trusted for critical work (do not use it to implement a buildd if you plan to rebuild the whole distro for example, its fine for home use to do testbuilds of packages or rolling chroots for creating root filesystems that you want to run on real hardware later on though)

Setting up an ARM chroot on your x86 machine

To use an arm eabi enabled chroot on your i386 system, install the qemu-user-static package.

sudo apt-get update
sudo apt-get install qemu-user-static

And create the chroot with the included debootstrap wrapper script (it takes/requires the same options debootstrap uses)

ogra@osiris:~$ sudo qemu-debootstrap --arch armhf vivid eabi-chroot
[sudo] password for ogra: 
I: Retrieving Release
I: Retrieving Packages

...

I: Base system installed successfully.
arm-eabi chroot successfully created in eabi-chroot
ogra@osiris:~$ sudo chroot eabi-chroot
root@osiris:/# uname -m
armv7l

Now you can build/test packages etc, the chroot works like any other x86 chroot on your system as long as you have the qemu-arm-static package installed with the advantage that you can make use of all resources your host system provides (CPU speed, RAM, diskspeed etc)

ARM/BuildEABIChroot (last edited 2016-08-17 22:35:01 by mariogrip)