Created attachment 2158 [details] qemu-native-1.7.0-r0_fail log
Can you provide the log.do_compile that includes the failure itself? /home/sean/works/P2041/SDK/QorIQ-SDK-V1.6-20140619-yocto/build_p2041rdb_release/tmp/work/i686-linux/qemu-native/1.7.0-r0/temp/log.do_compile.22204 Also can you confirm what version your host's gcc compiler is?
Created attachment 2177 [details] log.do_compile.22204
gcc (Ubuntu/Linaro 4.7.3-1ubuntu1) 4.7.3
Have you tried to clean qemu-native and then building it again? This looks like the kind of error you might see if you'd previously interrupted a build and the files were not left in a clean state...
This issue still occurs in clean state. Please refer to the log attached.
Created attachment 2282 [details] build fail log
This failure seems to be yet again different, you are running out of memory now with this "Cannot allocate memory", so not really conclusive. What kind of machine are you building this on (how much memory?) These errors are kind of random at this point one in building Qemu-native, another building python-native building the sysroot. Is the failure in qemu-native the same as the original one? Did you do a bitbake -c cleansstate qemu-native and then just build bitbake qemu-native
I am waiting for a response to my last comment from the original submitter
I am sorry for late response. It looks like same as original one. Yes I did, but the failure still occurred. I had used Xubuntu_14.04 on VMware. I will try it again using SDK_1.7.
Answer given
I am sorry to continue to ask questions, but I am not sure you answered my first set sufficiently. Based on your answer you appear to be building the Yocto Project in a VM itself, with how much memory (asked last time)? While both errors occur during the compilation of qemu-native are they consistent? Do both fail during the linkage and involve translate.o? The second failure as mentioned above also has a python failure that clearly shows out of memory.
As we have not received a reply in the last 60+ days, and as noted this is being run in a VM with limited memory (based on the failure modes) and as such not something we will fix. If there is a different issue that is not related to low memory, please provide the additional information requested and reopen if you feel we have closed this prematurely.