From: Gary Thomas <gary@mlbassoc.com>
To: Khem Raj <raj.khem@gmail.com>,
Praveenreddy Padamati <praveenreddy.p@hcl.com>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: chromium browser
Date: Mon, 7 Mar 2016 12:43:28 +0100 [thread overview]
Message-ID: <56DD6960.40902@mlbassoc.com> (raw)
In-Reply-To: <CAMKF1spOi8RbduxxwJHtUx_Xv69YO9nX7kr3fWBd4haMsL8OGQ@mail.gmail.com>
On 2016-03-07 12:05, Khem Raj wrote:
> What is your build machine configuration and look at log.do_cpmpile it might have some info
>
Also note that depending on your linker choice the build can need a lot of RAM and if your
build machine doesn't have enough you'll spend a lot of time swapping. I would suggest that
your build host has at least 4GB RAM to build chromium.
> On Mar 7, 2016 5:57 PM, "Praveenreddy Padamati" <praveenreddy.p@hcl.com <mailto:praveenreddy.p@hcl.com>> wrote:
>
> Hi,
>
> Thanks for the reply. It took more than 24 hours and then we stopped it.
>
> Thanks
> Praveen Reddy P
>
> -----Original Message-----
> From: bitbake-devel-bounces@lists.openembedded.org <mailto:bitbake-devel-bounces@lists.openembedded.org>
> [mailto:bitbake-devel-bounces@lists.openembedded.org <mailto:bitbake-devel-bounces@lists.openembedded.org>] On
> Behalf Of Gary Thomas
> Sent: Monday, March 07, 2016 2:42 PM
> To: bitbake-devel@lists.openembedded.org <mailto:bitbake-devel@lists.openembedded.org>
> Subject: Re: [bitbake-devel] chromium browser
>
> On 2016-03-07 09:30, Praveenreddy Padamati wrote:
> > Hi,
> >
> > When I added chromium browser in yocto build configuration then bitbake is stucking at do compile. Can you please
> help me?
> >
>
> How long have you waited? Depending on your target and host/build settings, building chromium can take a LONG time
> (measured in hours)
>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2016-03-07 11:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 8:30 chromium browser Praveenreddy Padamati
2016-03-07 9:11 ` Gary Thomas
2016-03-07 10:57 ` Praveenreddy Padamati
2016-03-07 11:05 ` Khem Raj
2016-03-07 11:43 ` Gary Thomas [this message]
2016-03-08 7:03 ` Praveenreddy Padamati
-- strict thread matches above, loose matches on Subject: below --
2011-02-07 4:52 yogesh lal
2011-02-07 12:15 ` Gary Thomas
2011-02-07 12:51 ` embedded.yogesh
2011-02-07 18:23 ` Darren Hart
2011-02-07 18:35 ` Gary Thomas
2011-02-08 4:02 ` embedded.yogesh
2011-02-21 5:33 ` embedded.yogesh
2011-02-22 11:13 ` Richard Purdie
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=56DD6960.40902@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=praveenreddy.p@hcl.com \
--cc=raj.khem@gmail.com \
/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.