How to properly enforce an ARM OABI build?

How to properly enforce an ARM OABI build?

[Sergey 'Jin' Bostandzhyan]

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

Re: How to properly enforce an ARM OABI build?

[Khem Raj]

[-- Attachment #1: Type: text/plain, Size: 343 bytes --]

Sergey 'Jin' Bostandzhyan wrote:
> 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"

may be use '=' instead of ':='


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 258 bytes --]

Re: How to properly enforce an ARM OABI build?

[Sergey 'Jin' Bostandzhyan]

On Tue, Apr 15, 2008 at 09:09:42AM -0700, Khem Raj wrote:
> > MACHINE="armv4t"
> > DISTRO="angstrom-2007.1"
> > TARGET_OS :="linux"
> > ARM_ABI := "oabi"
> 
> may be use '=' instead of ':='
 
I did try that before trying := but there was no difference...

Re: How to properly enforce an ARM OABI build?

[Khem Raj]

you can also try to comment out

ARM_ABI ?= "${@['','oabi'][bb.data.getVar('MACHINE',d) in
['collie','h3600', 'h3800', 'simpad', 'htcwallaby']]}"

and check

On Tue, Apr 15, 2008 at 9:39 AM, Sergey 'Jin' Bostandzhyan
<jin@mediatomb.cc> wrote:
> On Tue, Apr 15, 2008 at 09:09:42AM -0700, Khem Raj wrote:
>  > > MACHINE="armv4t"
>  > > DISTRO="angstrom-2007.1"
>  > > TARGET_OS :="linux"
>  > > ARM_ABI := "oabi"
>  >
>  > may be use '=' instead of ':='
>
>  I did try that before trying := but there was no difference...
>
>
>
>
>
>  _______________________________________________
>  Openembedded-devel mailing list
>  Openembedded-devel@lists.openembedded.org
>  http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: How to properly enforce an ARM OABI build?

[Sergey 'Jin' Bostandzhyan]

On Tue, Apr 15, 2008 at 09:47:35AM -0700, Khem Raj wrote:
> you can also try to comment out
> 
> ARM_ABI ?= "${@['','oabi'][bb.data.getVar('MACHINE',d) in
> ['collie','h3600', 'h3800', 'simpad', 'htcwallaby']]}"
> 
> and check

tried this without any luck, but then it struck me - someone was rewriting my
TARGET_OS! 

this someone is angstrom-uclibc.inc:

TARGET_OS_UC = "linux${@['-uclibc','-uclibcgnueabi'][bb.data.getVar('TARGET_ARCH',d,1) in ['arm', 'armeb'] and bb.data.getVar('MACHINE',d) not in ['collie','h3600', 'h3800', 'simpad', 'htcwallaby']]}"
TARGET_OS = "${@['${TARGET_OS_UC}', 'uclinux-uclibc'][bb.data.getVar('TARGET_ARCH',d)  in ['bfin']]}"

So I tried to set TARGET_OS to "linux-uclibc" in my local.conf and I 
commented out the lines in  angstrom-uclibc.inc - and it worked.

The question now is - how could this be solved cleanly in Angstrom?

Would this be an option:
TARGET_OS ?= "${@['${TARGET_OS_UC}', 'uclinux-uclibc'][bb.data.getVar('TARGET_ARCH',d)  in ['bfin']]}"

Kind regards,
Jin

> 
> On Tue, Apr 15, 2008 at 9:39 AM, Sergey 'Jin' Bostandzhyan
> <jin@mediatomb.cc> wrote:
> > On Tue, Apr 15, 2008 at 09:09:42AM -0700, Khem Raj wrote:
> >  > > MACHINE="armv4t"
> >  > > DISTRO="angstrom-2007.1"
> >  > > TARGET_OS :="linux"
> >  > > ARM_ABI := "oabi"
> >  >
> >  > may be use '=' instead of ':='
> >
> >  I did try that before trying := but there was no difference...
> >
> >
> >
> >
> >
> >  _______________________________________________
> >  Openembedded-devel mailing list
> >  Openembedded-devel@lists.openembedded.org
> >  http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> >
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: How to properly enforce an ARM OABI build?

[Khem Raj]

>  The question now is - how could this be solved cleanly in Angstrom?
>
>  Would this be an option:
>  TARGET_OS ?= "${@['${TARGET_OS_UC}', 'uclinux-uclibc'][bb.data.getVar('TARGET_ARCH',d)  in ['bfin']]}"
>

looks ok.