X32 abi: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(Created page with "==Vision== Incorporate toolchain components and other bits (binutils, gcc, glibc, gdb, kernel, linux-libc-headers) into a meta-x32 layer; And added needed infrastructure into the...")
 
(After meta-x32 got integrated to oe-core, we don't need meta-x32 layer for x32 support. Update the wikipage.)
 
(5 intermediate revisions by 2 users not shown)
Line 2: Line 2:
Incorporate toolchain components and other bits (binutils, gcc, glibc, gdb, kernel, linux-libc-headers) into a meta-x32 layer; And added needed infrastructure into the oe-core/yocto tree so that meta-x32 layer can work on top; so that one can build complete images with x32 abi binaries.
Incorporate toolchain components and other bits (binutils, gcc, glibc, gdb, kernel, linux-libc-headers) into a meta-x32 layer; And added needed infrastructure into the oe-core/yocto tree so that meta-x32 layer can work on top; so that one can build complete images with x32 abi binaries.


==Current Status as of 2011/07/14==
meta-x32 changes were integrated into OE-Core.


==X32 poky setup==


==Tasks==
* Add these lines to local.conf
* Create x32-layer & populate x32 specific recipes in it - done
MACHINE = "qemux86-64"
** create gcc-4.7, glibc2-14, kernel-2.6.38.y & other working recipes
DEFAULTTUNE = "x86-64-x32"
* Get core-image-minimal image building and running - done
** Fix the recipes which break with x32- Fixed glib-2.0, openssl, udev, busybox
*Integrate infrastructure pieces of x32 integrated in oe-core/yocto
** qemux32 change
** siteinfo changes
*** create a new tripplet for x32,
*** support multiple ABIs per architecture
** multilib changes will be needed soon
* assess how much work somehting like X11 and maybe sato would be
*List all the recipes which fail with x32 toolchain
** [[x32-broken-recipes-list]]
* try and find some way of assessing performance

Latest revision as of 11:55, 27 January 2016

Vision

Incorporate toolchain components and other bits (binutils, gcc, glibc, gdb, kernel, linux-libc-headers) into a meta-x32 layer; And added needed infrastructure into the oe-core/yocto tree so that meta-x32 layer can work on top; so that one can build complete images with x32 abi binaries.

meta-x32 changes were integrated into OE-Core.

X32 poky setup

  • Add these lines to local.conf
MACHINE = "qemux86-64"
DEFAULTTUNE = "x86-64-x32"
Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=X32_abi&oldid=17325"