All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: qemu needs > 2 GB of RAM to build?
Date: Fri, 18 Nov 2011 11:59:19 -0800	[thread overview]
Message-ID: <4EC6B917.90007@linux.intel.com> (raw)
In-Reply-To: <CAMKF1spQ5roygTCMRtZ5nhfhV+S9520tJYdV5Lyt-MB-Je1XZA@mail.gmail.com>



On 18/11/11 11:49, Khem Raj wrote:
> On Fri, Nov 18, 2011 at 11:39 AM, Scott Garman <scott.a.garman@intel.com> wrote:
>> Hi all,
>>
>> I'm testing building core-image-minimal in a resource-constrained
>> environment (a VirtualBox VM with 2300 MB of RAM allocated to it). With
>> PARALLEL_MAKE set to -j4 (the VM does have two CPUs allocated), I'm finding
>> that the build of qemu-native fails because the OOM killer steps in and
>> kills gcc. This is happening during the linking phase of building qemu.

What's BB_NUMBER_THREADS set to? I had to reduce to 1 to build
qemu-native on a laptop with 2GB RAM. iirc it had a habit of linking
something equally large such as eglibc, qt or the kernel at the same time.


> what distro are you running on guest ? it could be something wrong
> with the distro gcc or system

I've seen this on F14 (Gnome 2.x) and F15 (Gnome 3) with a laptop with
only 2GB RAM.

> 
>> If this is true, I assume it would pretty much mean that no one can build
>> our images without more than 2 GB of RAM. Is this true? Is this something
>> for us to be concerned about?
> 
> I have not seen such an error on a system which has 2G RAM all builds
> qemu-native fine here

I think BB_NUMBER_THREADS is the key here. And whether you're running
much in the way of a desktop environment.

Joshua
-- 
Joshua Lock
        Yocto Project "Johannes factotum"
        Intel Open Source Technology Centre



  reply	other threads:[~2011-11-18 20:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 19:39 qemu needs > 2 GB of RAM to build? Scott Garman
2011-11-18 19:49 ` Khem Raj
2011-11-18 19:59   ` Joshua Lock [this message]
2011-11-18 20:24     ` Scott Garman
2011-11-18 20:28       ` Joshua Lock
2011-11-18 21:17       ` Martin Jansa
2011-11-18 21:42         ` Scott Garman
2011-11-21  0:54 ` Ni Qingliang
2011-12-03 20:03 ` Khem Raj
2011-12-05  0:40   ` Ni Qingliang

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=4EC6B917.90007@linux.intel.com \
    --to=josh@linux.intel.com \
    --cc=openembedded-core@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 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.