X32 abi: Difference between revisions
From Yocto Project
Jump to navigationJump to search
Nitinkamble (talk | contribs) (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...") |
Nitinkamble (talk | contribs) |
||
| Line 1: | Line 1: | ||
==Vision== | ==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. | 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. | ||
==Tasks== | ==Tasks== | ||
Revision as of 18:42, 14 July 2011
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.
Tasks
- Create x32-layer & populate x32 specific recipes in it - done
- create gcc-4.7, glibc2-14, kernel-2.6.38.y & other working recipes
- 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
- try and find some way of assessing performance
