X32 abi - Revision history

Maxin B. John: After meta-x32 got integrated to oe-core, we don't need meta-x32 layer for x32 support. Update the wikipage.

2016-01-27T11:55:42Z

After meta-x32 got integrated to oe-core, we don't need meta-x32 layer for x32 support. Update the wikipage.

@@ 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.
-Moving the vision forward to 1.3, we have now integrated the meta-x32 changes into OE-Core, such that a build of
+meta-x32 changes were integrated into OE-Core.
 ==X32 poky setup==
-For Edison & Denzil (1.2 and earlier), you need the meta-x32 layer, this is NOT needed for 1.3 and later
+* Add these lines to local.conf
   MACHINE = "qemux86-64"
   DEFAULTTUNE = "x86-64-x32"

SaulWold at 16:17, 24 September 2012

2012-09-24T16:17:29Z

← Older revision		Revision as of 16:17, 24 September 2012
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.

			Moving the vision forward to 1.3, we have now integrated the meta-x32 changes into OE-Core, such that a build of
			x32 does not require the meta-x32 layer. If you are using older source base, you will still need meta-x32. Moving
			forward there is a list of items that need to be fixed for world build (see below)

	==Status==		==Status==
			1.2 Status:
	* The meta-x32 layer is hosting the x32 tollchain recipes now		* The meta-x32 layer is hosting the x32 tollchain recipes now
	* core-image-sato can build and run under qemu		* core-image-sato can build and run under qemu
	* Many recipes have been fixed for compilation with x32 toolchain.		* Many recipes have been fixed for compilation with x32 toolchain.

			1.3 Status:
			* x32 toolchain and kernel bits are part of OE-Core now
			* core-image-sato can build and run under qemux86-64
			* Most recipes have been fixed.

	==X32 poky setup==		==X32 poky setup==
	*add meta-x32 layer ~~- For Edison and Denzil~~, this is ~~not need~~ for 1.3
			For Edison & Denzil (1.2 and earlier), you need the meta-x32 layer, this is NOT needed for 1.3 and later
			*add meta-x32 layer
	** git clone x32 layer		** git clone x32 layer
	git clone git://git.yoctoproject.org/experimental/meta-x32		git clone git://git.yoctoproject.org/experimental/meta-x32

SaulWold: /* X32 poky setup */

2012-09-12T21:55:01Z

X32 poky setup

← Older revision		Revision as of 21:55, 12 September 2012
Line 8:		Line 8:

	==X32 poky setup==		==X32 poky setup==
	*add meta-x32 layer		*add meta-x32 layer - For Edison and Denzil, this is not need for 1.3
	** git clone x32 layer		** git clone x32 layer
	git clone git://git.yoctoproject.org/experimental/meta-x32		git clone git://git.yoctoproject.org/experimental/meta-x32
Line 23:		Line 23:
	"		"

	* And add these lines to local.conf		* And add these lines to local.conf - for all releases
	MACHINE = "qemux86-64"		MACHINE = "qemux86-64"
	DEFAULTTUNE = "x86-64-x32"		DEFAULTTUNE = "x86-64-x32"

Nitinkamble at 20:39, 10 January 2012

2012-01-10T20:39:12Z

@@ Line 1: / Line 1: @@
 ==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==
 * try and find some way of assessing performance

Nitinkamble: /* Tasks */

2011-08-08T21:58:22Z

Tasks

← Older revision		Revision as of 21:58, 8 August 2011
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 ~~somehting~~ like X11 and maybe sato would be		* 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

Nitinkamble: /* Current Status as of 2011/07/14 */

2011-07-14T18:42:38Z

Current Status as of 2011/07/14

← Older revision		Revision as of 18:42, 14 July 2011
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.

	~~==Current Status as of 2011/07/14==~~


	==Tasks==		==Tasks==

Nitinkamble: 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..."

2011-07-14T18:42:15Z

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..."

New page

==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.

==Current Status as of 2011/07/14==

==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
** [[x32-broken-recipes-list]]
* try and find some way of assessing performance