From: Sergey 'Jin' Bostandzhyan <jin@mediatomb.cc>
To: openembedded-devel@lists.openembedded.org
Subject: How to properly enforce an ARM OABI build?
Date: Tue, 15 Apr 2008 14:29:02 +0200 [thread overview]
Message-ID: <20080415122902.GA13726@deadlock.dhs.org> (raw)
Hi,
I want to build Angstrom for ARM OABI and I'm struggling to get the settings
right.
I'm using org.openembedded.stable and I tried this in my local conf:
MACHINE="armv4t"
DISTRO="angstrom-2007.1"
TARGET_OS :="linux"
ARM_ABI := "oabi"
ANGSTROM_MODE = "uclibc"
TARGET_FPU = "soft"
ENABLE_BINARY_LOCALE_GENERATION = "0"
My machine configuration does not do anything special either:
PACKAGE_EXTRA_ARCHS = "armv4 armv4t"
TARGET_ARCH = "arm"
require conf/machine/include/tune-arm920t.inc
Now.. I saw that Angstrom is using the ARM_ABI variable:
ARM_ABI ?= "${@['','oabi'][bb.data.getVar('MACHINE',d) in ['collie','h3600', 'h3800', 'simpad', 'htcwallaby']]}"
require conf/distro/include/angstrom${ARM_ABI}.inc
Since it's ?= I should be able to override it, right?
The directory in the work dir also look interesting:
arm-oabi-angstrom-linux-uclibcgnueabi
And the toolchain got created as arm-angstrom-linux-uclibcgnueabi-*, the
produced binaries are also EABI.
What am I missing? How do I force an OABI build for my machine?
Kind regards,
Jin
next reply other threads:[~2008-04-15 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-15 12:29 Sergey 'Jin' Bostandzhyan [this message]
2008-04-15 16:09 ` How to properly enforce an ARM OABI build? Khem Raj
2008-04-15 16:39 ` Sergey 'Jin' Bostandzhyan
2008-04-15 16:47 ` Khem Raj
2008-04-16 9:42 ` Sergey 'Jin' Bostandzhyan
2008-04-19 22:56 ` Khem Raj
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=20080415122902.GA13726@deadlock.dhs.org \
--to=jin@mediatomb.cc \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.