From: Ni Qingliang <niqingliang@insigma.com.cn>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: qemu needs > 2 GB of RAM to build?
Date: Mon, 21 Nov 2011 08:54:55 +0800 [thread overview]
Message-ID: <1321836895.1264.50.camel@localhost.localdomain> (raw)
In-Reply-To: <4EC6B45A.9060107@intel.com>
I have encountered the same problem on archlinux in VM.
after googled it, maybe it is GCC's defect
On Sat, 2011-11-19 at 03:39 +0800, Scott Garman 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.
>
> 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
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Yi Qingliang
niqingliang@insigma.com.cn
https://niqingliang2003.wordpress.com
next prev parent reply other threads:[~2011-11-21 1:02 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
2011-11-21 0:54 ` Ni Qingliang [this message]
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=1321836895.1264.50.camel@localhost.localdomain \
--to=niqingliang@insigma.com.cn \
--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