All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: meta-freescale@yoctoproject.org
Subject: Re: Error: Adding chromium browser + fsl-image-gui (Yocto - Dora)
Date: Fri, 09 May 2014 22:18:58 +0200	[thread overview]
Message-ID: <536D3832.4010104@pseudoterminal.org> (raw)
In-Reply-To: <CAPhrY5Njfph37Gg4K33hPrtDKS2DZXRttk1bhqWubzBqukQimA@mail.gmail.com>

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

On 2014-05-04 15:35, Dmitriy B. wrote:
> 2014-05-04 12:26 GMT+04:00 Benuvel GnanaKirubakaran, Jv. 
> <benuvelj@iwavesystems.com <mailto:benuvelj@iwavesystems.com>>:
>
>
>     could you help us to resolve the issue?
>
>
> Add meta-gnome and meta-ruby layers. Then add LICENSE_FLAGS_WHITELIST 
> to have x264/libav enabled, chromium depends on them.
>
> Also be sure to have at least 32GB of RAM on your build machine, I 
> already tried to build chromium on 8GB+4GB swap and on 16GB+8GB swap 
> machines without success, it fails at LINK stage with oom-killer being 
> invoked.
>
>     --
>     Thanks & Regards,
>     Benuvel Jv
>
>
> Best Regards,
> Dmitriy Beykun
>
>

I submitted patches to meta-browser that add a packageconfig for 
component builds. With them, it becomes possible to build even with 8 GB 
RAM (though swap will be used, and the disk cache will not work optimally).

[-- Attachment #2: Type: text/html, Size: 2359 bytes --]

  reply	other threads:[~2014-05-09 20:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-04  8:26 Error: Adding chromium browser + fsl-image-gui (Yocto - Dora) Benuvel GnanaKirubakaran, Jv.
2014-05-04 13:35 ` Dmitriy B.
2014-05-09 20:18   ` Carlos Rafael Giani [this message]
2014-05-06 10:38 ` Somashekar
2014-05-09 20:11   ` Lauren Post
2014-05-09 20:20   ` Carlos Rafael Giani

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=536D3832.4010104@pseudoterminal.org \
    --to=dv@pseudoterminal.org \
    --cc=meta-freescale@yoctoproject.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.