All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Schuster <theBohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: "armv6" override not used
Date: Wed, 14 Jan 2009 03:17:23 +0100	[thread overview]
Message-ID: <496D4B33.60102@gmx.net> (raw)

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

Hi,
I am building chinook-compat for the n800 when it comes to libffi the
successful build depends on this line:

TARGET_CC_ARCH_append_armv6 =3D " -D__SOFTFP__"

However the build fails because __SOFTFP__ isn't defined and bitbake -i
reveals:

BB>> peek libffi-2.0+gcc4.3.2 TARGET_CC_ARCH
SHELL: This command needs to parse bbfiles...
NOTE: Handling BitBake files: - (6521/6521) [100 %]
NOTE: Parsing finished. 0 cached, 6238 parsed, 283 skipped, 0 masked.

-march=3Darmv6j -mtune=3Darm1136jf-s -mfpu=3Dvfp -mfloat-abi=3Dsoftfp
-mno-thumb-interwork -mno-thumb
BB>>

It looks like something is wrong with the OVERRIDES variable. It has
this value:

local:nokia800:chinook-compat:linux-gnueabi:arm:build-linux:fail-fast:pn-=
libffi

Checking the same variable in an Angstrom build for the BeagleBoard
(armv7a - needs the same hack) it looks like this:

local:beagleboard:angstrom:linux-gnueabi:arm:build-linux:fail-fast:pn-lib=
ffi:armv7a

Something went wrong, but what?

Regards
Robert


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

             reply	other threads:[~2009-01-14  2:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14  2:17 Robert Schuster [this message]
2009-01-14  7:07 ` "armv6" override not used Koen Kooi
2009-01-14 10:57   ` Robert Schuster
2009-01-14 11:04     ` Phil Blundell
2009-01-14 13:51       ` Robert Schuster
2009-01-14 14:44         ` Phil Blundell
2009-01-15  4:08           ` Khem Raj
2009-01-14 14:41 ` Koen Kooi

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=496D4B33.60102@gmx.net \
    --to=thebohemian@gmx.net \
    --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.