X32 abi: Difference between revisions
From Yocto Project
Jump to navigationJump to search
Nitinkamble (talk | contribs) |
Nitinkamble (talk | contribs) (→Tasks) |
||
| Line 8: | Line 8: | ||
** Fix the recipes which break with x32- Fixed glib-2.0, openssl, udev, busybox | ** Fix the recipes which break with x32- Fixed glib-2.0, openssl, udev, busybox | ||
*Integrate infrastructure pieces of x32 integrated in oe-core/yocto | *Integrate infrastructure pieces of x32 integrated in oe-core/yocto | ||
** qemux32 change | ** qemux32 change - not needed anymore | ||
** siteinfo changes | ** siteinfo changes - RP accepted for master | ||
*** create a new tripplet for x32, | *** create a new tripplet for x32, -- solved differently with ABIEXTENSION | ||
*** support multiple ABIs per architecture | *** support multiple ABIs per architecture | ||
** multilib changes will be needed soon | ** multilib changes will be needed soon | ||
* assess how much work | * assess how much work something like X11 and maybe sato would be | ||
*List all the recipes which fail with x32 toolchain | *List all the recipes which fail with x32 toolchain | ||
** [[x32-broken-recipes-list]] | ** [[x32-broken-recipes-list]] | ||
* try and find some way of assessing performance | * try and find some way of assessing performance | ||
Revision as of 21:58, 8 August 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 - not needed anymore
- siteinfo changes - RP accepted for master
- create a new tripplet for x32, -- solved differently with ABIEXTENSION
- support multiple ABIs per architecture
- multilib changes will be needed soon
- assess how much work something like X11 and maybe sato would be
- List all the recipes which fail with x32 toolchain
- try and find some way of assessing performance
