From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 57CA6E0073A; Fri, 9 May 2014 13:19:03 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: * X-Spam-Status: No, score=1.3 required=5.0 tests=HTML_MESSAGE,RDNS_NONE, SPF_HELO_PASS autolearn=no version=3.3.1 X-Spam-HAM-Report: * -0.0 SPF_HELO_PASS SPF: HELO matches SPF record * 0.0 HTML_MESSAGE BODY: HTML included in message * 1.3 RDNS_NONE Delivered to internal network by a host with no rDNS Received: from ptmx.org (unknown [178.63.28.110]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id ED9CCE00478 for ; Fri, 9 May 2014 13:19:00 -0700 (PDT) Received: from [192.168.178.14] (chello080108088242.14.11.vie.surfer.at [80.108.88.242]) by ptmx.org (Postfix) with ESMTPSA id AB6C82997B for ; Fri, 9 May 2014 22:18:59 +0200 (CEST) Message-ID: <536D3832.4010104@pseudoterminal.org> Date: Fri, 09 May 2014 22:18:58 +0200 From: Carlos Rafael Giani User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: meta-freescale@yoctoproject.org References: <20140504042604.16786jtj1xgod9jw@iwavesystems.com> In-Reply-To: Subject: Re: Error: Adding chromium browser + fsl-image-gui (Yocto - Dora) X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 May 2014 20:19:03 -0000 Content-Type: multipart/alternative; boundary="------------060108040804000401010200" --------------060108040804000401010200 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 2014-05-04 15:35, Dmitriy B. wrote: > 2014-05-04 12:26 GMT+04:00 Benuvel GnanaKirubakaran, Jv. > >: > > > 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). --------------060108040804000401010200 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit

On 2014-05-04 15:35, Dmitriy B. wrote:

2014-05-04 12:26 GMT+04:00 Benuvel GnanaKirubakaran, Jv. <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).
--------------060108040804000401010200--