IMX8M - Yocto - Build Error -

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

IMX8M - Yocto - Build Error -

Jump to solution
2,813 Views
darsh_dev
Contributor V
Hello,
 
I try to setup imx-5.4.47-2.2.0 repo for IMX8qxpcomek.
follow the below steps to build imx-image-full image
 
$ mkdir imx-yocto-bsp
$ cd imx-yocto-bsp
$ repo init -u https://source.codeaurora.org/external/imx/imx-manifest -b imx-linux-zeus -m imx-5.4.47-2.2.0.xml
$ repo sync
 
$ DISTRO=fsl-imx-xwayland MACHINE=imx8qxpc0mek source imx-setup-release.sh -b bld-imx8qxp-mek
 
$ bitbake imx-image-full
 
it through below error while do compile some packages i.e opencv, qtbase, qtwayland....
 
aarch64-poky-linux-g++: fatal error: Killed signal terminated program cc1plus
 
by setting BB_NUMBER_THREADS=1
or separately bulid the package then not getting the error. But we want proper solution instead of reducing the thread.
0 Kudos
1 Solution
2,802 Views
Bio_TICFSL
NXP TechSupport
NXP TechSupport

Hello darshak,

Most likely that is your problem. Running make -j 8 runs lots of process which use more memory. The problem above occurs when your system runs out of memory. In this case rather than the whole system falling over, the operating systems runs a process to score each process on the system. The one that scores the highest gets killed by the operating system to free up memory. If the process that is killed is cc1plus, gcc (perhaps incorrectly) interprets this as the process crashing and hence assumes that it must be a compiler bug. But it isn't really, the problem is the OS killed cc1plus, rather than it crashed.

If this is the case, you are running out of memory. So run perhaps make -j 4 instead. This will mean fewer parallel jobs and will mean the compilation will take longer but hopefully will not exhaust your system memory.

You can run again with BBTHREADS=1 but you need erase all your compilation bitbake -c clean

 

Regards

 

View solution in original post

2 Replies
2,803 Views
Bio_TICFSL
NXP TechSupport
NXP TechSupport

Hello darshak,

Most likely that is your problem. Running make -j 8 runs lots of process which use more memory. The problem above occurs when your system runs out of memory. In this case rather than the whole system falling over, the operating systems runs a process to score each process on the system. The one that scores the highest gets killed by the operating system to free up memory. If the process that is killed is cc1plus, gcc (perhaps incorrectly) interprets this as the process crashing and hence assumes that it must be a compiler bug. But it isn't really, the problem is the OS killed cc1plus, rather than it crashed.

If this is the case, you are running out of memory. So run perhaps make -j 4 instead. This will mean fewer parallel jobs and will mean the compilation will take longer but hopefully will not exhaust your system memory.

You can run again with BBTHREADS=1 but you need erase all your compilation bitbake -c clean

 

Regards

 

2,753 Views
darsh_dev
Contributor V

It was the issue, because of the SWAP partition size on Server, After increasing the SWAP size (> 2XRAM size), issue not seen with higher number of -j 8 or >8.

0 Kudos