All of lore.kernel.org
 help / color / mirror / Atom feed
From: Riko Ho <antonius.riko@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	Gunnar Andersson <gandersson@genivi.org>
Subject: Re: Compiling meta-browser ==>chromium ? cleaning ?
Date: Wed, 21 Jun 2017 09:53:48 +0800	[thread overview]
Message-ID: <61e45e0b-1fda-ecf5-51eb-437284c94d02@gmail.com> (raw)
In-Reply-To: <CAMKF1sp_5+1N_+okGXxZMREir62snRDk+BtbwDMz+t5SUYo5pg@mail.gmail.com>

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

Ok, thanks a lot for the parameter idea, where will I put that ? 
local.conf, bblayers.conf ?


On 20/06/17 13:08, Khem Raj wrote:
> On Mon, Jun 19, 2017 at 8:32 PM, Riko Ho <antonius.riko@gmail.com> wrote:
>> My memory is 8Gb and swap 8Gb, 8 cores i7, may be a homemade cluster can
>> help ?
>>
> add something like
>
> EXTRA_OEGYP_prepend = " -Dcomponent=shared_library
> -Dremove_webcore_debug_symbols=1 -Dfastbuild=1 "
>
> and see if that helps.
>
>> I compiled firefox and it worked well, but still wondering why chromium
>> didn't work.
>>
>>
>> On 20/06/17 04:01, Khem Raj wrote:
>>
>> On Mon, Jun 19, 2017 at 7:21 AM, Jacobo Aragunde Pérez
>> <jaragunde@igalia.com> wrote:
>>
>> On 18/06/17 20:10, Gunnar Andersson wrote:
>>
>> Riko Ho <antonius.riko@gmail.com> wrote:
>>
>> Hello Everyone,
>>
>> I tried to compile chromium but never succeeded, took me already 12
>> hours and stopped on 99%, I used bitbake for doing it,
>>
>> Not sure what would cause it to just stop and it could have been some
>> temporary glitch?   Maybe you want to provide some logs of your build if
>> Martin's reference does not help.
>>
>> Just a heads-up, if it stopped at 99% it probably was in the linking
>> phase (you can check the logs under
>> tmp/work/$arch/chromium-wayland/$version/temp/log.do_compile to be
>> certain). This phase has a very high RAM demand, you could even need to
>> temporarily increase your swap space to go past that point.
>>
>> linker takes a whole lot of memory here, if you have < 8G of RAM
>> its likely to fail with out of memory errors. Can you check your dmesg
>> and see if there were such errors in there
>>
>> Best,
>> --
>> Jacobo Aragunde
>> Software Engineer at Igalia
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>>
>> --
>>
>> /*******/
>> Sent by Ubuntu LTS 16.04,
>> 谢谢,
>> Regards,
>> Riko Ho
>> /*******/

-- 
*

/*******/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/*******/

*

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

  reply	other threads:[~2017-06-21  1:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.66247.1497786545.15860.yocto@yoctoproject.org>
2017-06-18 18:10 ` Compiling meta-browser ==>chromium ? cleaning ? Gunnar Andersson
2017-06-19 14:21   ` Jacobo Aragunde Pérez
2017-06-19 20:01     ` Khem Raj
2017-06-20  3:32       ` Riko Ho
2017-06-20  5:08         ` Khem Raj
2017-06-21  1:53           ` Riko Ho [this message]
2017-06-21  2:28             ` Khem Raj
2017-06-21  4:38               ` Riko Ho
2017-06-21  4:42               ` Riko Ho
2017-06-21  7:37                 ` Gunnar Andersson
2017-06-21  8:18                   ` Riko Ho
2017-06-21  8:24                   ` Riko Ho
2017-06-23  3:40                   ` 47401300.usb-phy supply vcc not found, using dummy regulator Riko Ho
2017-06-24  4:52                   ` Compiling meta-browser ==>chromium ? cleaning ? Riko Ho
2017-06-14  4:10 bitbake core-image-web-kiosk question ? Riko Ho
2017-06-14  5:38 ` Khem Raj
2017-06-15  5:53   ` FriendlyArm Mini6410 ? Riko Ho
2017-06-15  6:05     ` Belisko Marek
2017-06-17 23:41       ` Compiling meta-browser ==>chromium ? cleaning ? Riko Ho
2017-06-18  7:49         ` Martin Jansa
2017-06-18  7:52           ` Riko Ho

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=61e45e0b-1fda-ecf5-51eb-437284c94d02@gmail.com \
    --to=antonius.riko@gmail.com \
    --cc=gandersson@genivi.org \
    --cc=raj.khem@gmail.com \
    --cc=yocto@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.