From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-browser] ARM support in Chromium
Date: Mon, 22 Feb 2016 13:47:27 +0100 [thread overview]
Message-ID: <56CB035F.9060008@mlbassoc.com> (raw)
In-Reply-To: <56CAFFD2.6090304@siemens.com>
On 2016-02-22 13:32, Pascal Bach wrote:
>
>
> Am 22.02.2016 um 11:44 schrieb Gary Thomas:
>> On 2016-02-22 11:32, Martin Jansa wrote:
>>> Yes it can, because cortex-a7 is armv7a.
>>
>> My build failed listing the board as not compatible
>> ERROR: Nothing PROVIDES 'chromium'
>> ERROR: chromium was skipped: incompatible with machine teton-p0381 (not in COMPATIBLE_MACHINE)
>
> I think it might be worth to have a look at your MACHINEOVERRIDES variable.
> bitbake -e should be of assistance here.
>
Good pointer - the ARM architecture is being set to armv7ve, not armv7a
This was changed (by Martin Jansa) in Poky commit c6a19917ec5350cdfc4053d14462609782613bbc
I suppose a patch to the chromium recipe to allow armv7ve is in order.
>>
>>> On Mon, Feb 22, 2016 at 11:30 AM, Gary Thomas <gary@mlbassoc.com> wrote:
>>>
>>>> A recent change to the chromium recipe restricts it to only
>>>> armv6 and armv7a. I've built (and successfully run) previous
>>>> versions of chromium on my LS102x board which is cortexa7hf.
>>>> It's not clear to me what arm revision that works out to be
>>>> (where does one look for this info?) but I'd like to see if
>>>> chromium can still be used on my board?
>>>>
>>>> Thanks for any pointers
>>
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2016-02-22 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 10:30 [meta-browser] ARM support in Chromium Gary Thomas
2016-02-22 10:32 ` Martin Jansa
2016-02-22 10:44 ` Gary Thomas
2016-02-22 12:32 ` Pascal Bach
2016-02-22 12:47 ` Gary Thomas [this message]
2016-02-22 21:38 ` Andre McCurdy
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=56CB035F.9060008@mlbassoc.com \
--to=gary@mlbassoc.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox