From: Robert Schuster <theBohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: "armv6" override not used
Date: Wed, 14 Jan 2009 11:57:36 +0100 [thread overview]
Message-ID: <496DC520.90601@gmx.net> (raw)
In-Reply-To: <gkk2ut$5m8$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 906 bytes --]
Hi,
Koen Kooi schrieb:
>> 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?
>
> Angstrom defines architecture overrides to make life easier for
> developers, other distros don't.
I see:
include/angstrom.inc:OVERRIDES .= ":${FEED_ARCH}"
Is that such a controversial feature? I think this should be part of all
distros.
Without this libffi breaks (on armv6 and arm7a) and in the future this
means that stuff like openjdk won't be buildable on these arches. :(
Regards
Robert
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 268 bytes --]
next prev parent reply other threads:[~2009-01-14 11:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 2:17 "armv6" override not used Robert Schuster
2009-01-14 7:07 ` Koen Kooi
2009-01-14 10:57 ` Robert Schuster [this message]
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=496DC520.90601@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.