From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: qemu needs > 2 GB of RAM to build?
Date: Fri, 18 Nov 2011 11:39:06 -0800 [thread overview]
Message-ID: <4EC6B45A.9060107@intel.com> (raw)
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.
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?
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next reply other threads:[~2011-11-18 19:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 19:39 Scott Garman [this message]
2011-11-18 19:49 ` qemu needs > 2 GB of RAM to build? Khem Raj
2011-11-18 19:59 ` Joshua Lock
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=4EC6B45A.9060107@intel.com \
--to=scott.a.garman@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.