Hey Manju,

I'd like to see if I can reproduce this, could you please send the the steps 
you followed?

Thanks!

Alejandro

-----Original Message-----
From: meta-xilinx-boun...@yoctoproject.org 
[mailto:meta-xilinx-boun...@yoctoproject.org] On Behalf Of Manjukumar 
Harthikote Matha
Sent: Sunday, January 14, 2018 10:20 PM
To: openembedded-core@lists.openembedded.org; yo...@yoctoproject.org; 
meta-xil...@yoctoproject.org
Subject: [meta-xilinx] liblzma: Memory allocation failed on do_package_rpm

All,

Has anybody seen this error?

Finished binary package job, result 0, filename (null)
error: create archive failed: cpio: write failed - Cannot allocate memory
error: liblzma: Memory allocation failederror: liblzma: Memory allocation 
failedFinished binary package job, result 2,

.......

RPM build errors:
|     Deprecated external dependency generator is used!
|     Deprecated external dependency generator is used!
|     Deprecated external dependency generator is used!
|     Deprecated external dependency generator is used!
|     Deprecated external dependency generator is used!
|     Deprecated external dependency generator is used!
|     Deprecated external dependency generator is used!
|     Deprecated external dependency generator is used!
|     Deprecated external dependency generator is used!
|     liblzma: Memory allocation failed    liblzma: Memory allocation failed    
liblzma: Memory allocation failed    liblzma: Memory allocation failed    
liblzma: Memory allocation failed    liblzma: Memory allocation failed

This happens in do_package_rpm task on various recipes, 
coreutils/libgpg/diffutils etc.

The host machine has good amount on memory, 256G to be exact. When I see the 
error and issue free -h command, I still see ~120G free memory available.
This is a RHEL 7.2 machine and I am running rocko baseline.

Any reason why this would happen? Where should I look to fix this issue?

Thanks,
Manju
This email and any attachments are intended for the sole use of the named 
recipient(s) and contain(s) confidential information that may be proprietary, 
privileged or copyrighted under applicable law. If you are not the intended 
recipient, do not read, copy, or forward this email message or any attachments. 
Delete this email message and any attachments immediately.
-- 
_______________________________________________
meta-xilinx mailing list
meta-xil...@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx
-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to