On Fri, Nov 18, 2011 at 11:39 AM, Scott Garman <scott.a.gar...@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. > > 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 think this could be because of gcc bug http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48190 that bug has now been fixed and backported to gcc-4.5 and gcc 4.6 branches as well however this fix has to go into the gcc in distro that you are running on build host we will get this fix into oe-core gcc as well but that may not help with qemu-native -Khem _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
