<div>Hi Aleksandar Nikolic,</div>
<div>&nbsp;</div>
<div>
<div>Yes, we need to use only the older Dunfell version. Initially, when I built the latest image, I did not face any issues&mdash;the image was successfully built. Afterward, I created my own layer and updated the BusyBox version to 1.35. Upon building using bitbake -c cleanall busybox and bitbake busybox, the updated BusyBox version was successfully built.</div>
<div>However, while compiling the complete image (for example, core-image-minimal), I observed an issue with GLIBC. To address this, I removed the layer I had added and rebuilt the image. Now, BusyBox has reverted to the backport version (1.31), but while jobs are running, cmake-native is also executing, and an error related to GLIBC 2.3.40 not being found is displayed.</div>
<div>I suspect this issue might be related to the local PC environment. Could you please suggest an alternative solution to fix this issue?</div>
<div>&nbsp;</div>
<div>Regards,</div>
<div>Sateesh</div>
</div>