From: nitin.a.kamble@intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Commits enabling x32 infrastructure in the master branch
Date: Wed, 27 Jul 2011 16:09:57 -0700 [thread overview]
Message-ID: <cover.1311806842.git.nitin.a.kamble@intel.com> (raw)
From: Nitin A Kamble <nitin.a.kamble@intel.com>
These commits add infrastructure to the oe-core/yocto to add the meta-x32 layer to build x32 images. core-image-minimal has been tested to work with this commits
=== How to build an image with x32 binaries
Add this layer on top of yocto/oe-core
http://git.pokylinux.org/cgit/cgit.cgi/experimental/meta-x32/
Add these lines in your conf/local.conf
MACHINE = "qemux86-64"
DEFAULTTUNE = "x86-64-x32"
TUNE_PKGARCH = "x86-64-x32"
And build the minimal image with command:
bitbake core-image-minimal
And then run it with qemu with this command:
runqemu qemux86-64 core-image-minimal
=== How to know if your binaries/libraries are x32:
Run the file command to know what type of elf binary is it. It should
be 32bit x86-64 elf binary as seen here:
$ file bin/busybox
bin/busybox: setuid ELF 32-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.35, not stripped
$file usr/lib/libz.so.1.2.5
usr/lib/libz.so.1.2.5: ELF 32-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, not stripped
The following changes since commit f94b781695cd8fa387daff16ecbf3987a0883018:
poky.conf: explicitly referenced preferred linux-yocto version (2011-07-27 09:56:56 -0700)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib nitin/x32
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/x32
Nitin A Kamble (4):
toolchain-scripts & other classes: add TARGET_LD_ARCH &
TARGET_AS_ARCH vars
siteinfo.bbclass: add entries for new x86_64 ABI targets
insane.bbclass: add entries for linux-gnu<ABI>
x86 tune inc files: add x32 abi tune parameters
meta/classes/allarch.bbclass | 2 ++
meta/classes/cross-canadian.bbclass | 2 ++
meta/classes/cross.bbclass | 2 ++
meta/classes/crosssdk.bbclass | 2 ++
meta/classes/insane.bbclass | 9 +++++++++
meta/classes/native.bbclass | 10 +++++++---
meta/classes/nativesdk.bbclass | 4 ++++
meta/classes/siteinfo.bbclass | 14 +++++++++++++-
meta/classes/toolchain-scripts.bbclass | 9 +++++----
meta/conf/bitbake.conf | 23 +++++++++++++++++------
meta/conf/machine/include/ia32/arch-ia32.inc | 23 ++++++++++++++++++++---
meta/conf/machine/include/tune-core2.inc | 4 ++++
meta/conf/machine/include/tune-x86_64.inc | 2 +-
13 files changed, 88 insertions(+), 18 deletions(-)
--
1.7.4.4
next reply other threads:[~2011-07-27 23:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 23:09 nitin.a.kamble [this message]
2011-07-27 23:09 ` [PATCH 1/4] toolchain-scripts & other classes: add TARGET_LD_ARCH & TARGET_AS_ARCH vars nitin.a.kamble
2011-07-27 23:09 ` [PATCH 2/4] siteinfo.bbclass: add entries for new x86_64 ABI targets nitin.a.kamble
2011-07-27 23:12 ` Tom Rini
2011-07-27 23:27 ` Kamble, Nitin A
2011-07-27 23:41 ` Tom Rini
2011-07-27 23:10 ` [PATCH 3/4] insane.bbclass: add entries for linux-gnu<ABI> nitin.a.kamble
2011-07-27 23:10 ` [PATCH 4/4] x86 tune inc files: add x32 abi tune parameters nitin.a.kamble
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1311806842.git.nitin.a.kamble@intel.com \
--to=nitin.a.kamble@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox