Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-browser][PATCH 2/2] chromium: Add recipes for 29.0.1518
Date: Tue, 28 May 2013 09:05:37 -0600	[thread overview]
Message-ID: <51A4C7C1.6050706@mlbassoc.com> (raw)
In-Reply-To: <1369604103-31315-2-git-send-email-raj.khem@gmail.com>

On 2013-05-26 15:35, Khem Raj wrote:
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> CC: Eric Bénard <eric@eukrea.com>
> CC: Denis Carikli <denis@eukrea.com>
> CC: Otavio Salvador <otavio@ossystems.com.br>
>
> ---
>   .../chromium-29.0.1518.2/armv6/include.gypi        |  8 ++
>   .../chromium-29.0.1518.2/armv6/oe-defaults.gypi    | 15 ++++
>   .../chromium-29.0.1518.2/armv7a/include.gypi       |  9 +++
>   .../chromium-29.0.1518.2/armv7a/oe-defaults.gypi   | 15 ++++
>   .../chromium-29.0.1518.2/i586/include.gypi         |  5 ++
>   .../chromium-29.0.1518.2/i586/oe-defaults.gypi     | 15 ++++
>   .../uninitialised-warning.patch                    | 90 ++++++++++++++++++++++
>   .../chromium/chromium-29.0.1518.2/unistd-2.patch   | 27 +++++++
>   .../chromium-29.0.1518.2/x86-64/include.gypi       |  5 ++
>   .../chromium-29.0.1518.2/x86-64/oe-defaults.gypi   | 15 ++++
>   recipes-browser/chromium/chromium_29.0.1518.2.bb   | 72 +++++++++++++++++
>   11 files changed, 276 insertions(+)
>   create mode 100644 recipes-browser/chromium/chromium-29.0.1518.2/armv6/include.gypi
>   create mode 100644 recipes-browser/chromium/chromium-29.0.1518.2/armv6/oe-defaults.gypi
>   create mode 100644 recipes-browser/chromium/chromium-29.0.1518.2/armv7a/include.gypi
>   create mode 100644 recipes-browser/chromium/chromium-29.0.1518.2/armv7a/oe-defaults.gypi
>   create mode 100644 recipes-browser/chromium/chromium-29.0.1518.2/i586/include.gypi
>   create mode 100644 recipes-browser/chromium/chromium-29.0.1518.2/i586/oe-defaults.gypi
>   create mode 100644 recipes-browser/chromium/chromium-29.0.1518.2/uninitialised-warning.patch
>   create mode 100644 recipes-browser/chromium/chromium-29.0.1518.2/unistd-2.patch
>   create mode 100644 recipes-browser/chromium/chromium-29.0.1518.2/x86-64/include.gypi
>   create mode 100644 recipes-browser/chromium/chromium-29.0.1518.2/x86-64/oe-defaults.gypi
>   create mode 100644 recipes-browser/chromium/chromium_29.0.1518.2.bb
   ... snip

Have you tried this?  I just built it for my ARMv7a (i.MX6Q SabreLite) and it
seems to hang up on any page that uses JavaScript.  Try most any of the links
on the "Chrome Help" page.

Maybe I'm missing something?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  parent reply	other threads:[~2013-05-28 15:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-26 21:35 [meta-browser][PATCH 1/2] chromium_24.0.1312.52.bb: Fix build with hardfp Khem Raj
2013-05-26 21:35 ` [meta-browser][PATCH 2/2] chromium: Add recipes for 29.0.1518 Khem Raj
2013-05-27  6:11   ` Eric Bénard
2013-05-28 15:05   ` Gary Thomas [this message]
2013-05-28 15:10     ` Eric Bénard
2013-05-28 15:11       ` Eric Bénard
2013-05-28 22:42       ` Gary Thomas

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=51A4C7C1.6050706@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