X32 abi: Difference between revisions
From Yocto Project
Jump to navigationJump to search
Nitinkamble (talk | contribs) (→Tasks) |
(After meta-x32 got integrated to oe-core, we don't need meta-x32 layer for x32 support. Update the wikipage.) |
||
(3 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. | ||
meta-x32 changes were integrated into OE-Core. | |||
==X32 poky setup== | |||
* Add these lines to local.conf | |||
MACHINE = "qemux86-64" | |||
* | DEFAULTTUNE = "x86-64-x32" | ||
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"