From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: qemu needs > 2 GB of RAM to build?
Date: Fri, 18 Nov 2011 13:42:15 -0800 [thread overview]
Message-ID: <4EC6D137.7020002@intel.com> (raw)
In-Reply-To: <20111118211740.GF3549@jama.jama.net>
On 11/18/2011 01:17 PM, Martin Jansa wrote:
> Why not enable more swap? It's slow but works for short peaks in mem
> usage. I have to extend our swap from 2G to 4G on VM with 2G RAM for
> some builds.. also needed during linking unstripped libs :/.
Thank you, Marin - this is an excellent idea. :)
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2011-11-18 21:48 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
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 [this message]
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=4EC6D137.7020002@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox