Dear Yocto Experts, Could you please help me to resolve this issue. ERROR: m4-native-1.4.18-r0 do_compile: oe_runmake failed Tried the following DISTRO=fsl-imx-wayland MACHINE=imx8mqevk source fsl-setup-release.sh -b build-wayland bitbake core-image-minimal The following is the summary of build | Makefile:1915: recipe for target 'close-stream.o' failed | make[3]: *** [close-stream.o] Segmentation fault (core dumped) | make[3]: *** Waiting for unfinished jobs.... | make[3]: Leaving directory '/home/valeo-cic/imx-yocto-bsp/build-wayland/tmp/work/x86_64-linux/m4-native/1.4.18-r0/build/lib' | Makefile:1674: recipe for target 'all' failed | make[2]: *** [all] Error 2 | make[2]: Leaving directory '/home/valeo-cic/imx-yocto-bsp/build-wayland/tmp/work/x86_64-linux/m4-native/1.4.18-r0/build/lib' | Makefile:1572: recipe for target 'all-recursive' failed | make[1]: *** [all-recursive] Error 1 | make[1]: Leaving directory '/home/valeo-cic/imx-yocto-bsp/build-wayland/tmp/work/x86_64-linux/m4-native/1.4.18-r0/build' | Makefile:1528: recipe for target 'all' failed | make: *** [all] Error 2 | ERROR: oe_runmake failed | WARNING: /home/valeo-cic/imx-yocto-bsp/build-wayland/tmp/work/x86_64-linux/m4-native/1.4.18-r0/temp/run.do_compile.29555:1 exit 1 from 'exit 1' | ERROR: Function failed: do_compile (log file is located at /home/valeo-cic/imx-yocto-bsp/build-wayland/tmp/work/x86_64-linux/m4-native/1.4.18-r0/temp/log.do_compile.29555) ERROR: Task (/home/valeo-cic/imx-yocto-bsp/sources/poky/meta/recipes-devtools/m4/m4-native_1.4.18.bb:do_compile) failed with exit code '1' NOTE: Tasks Summary: Attempted 100 tasks of which 0 didn't need to be rerun and 1 failed. Summary: 1 task failed: /home/valeo-cic/imx-yocto-bsp/sources/poky/meta/recipes-devtools/m4/m4-native_1.4.18.bb:do_compile Summary: There was 1 WARNING message shown. Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
Created attachment 4541 [details] Build Console Log
m4-native is very early in the build process. Its also a native recipe using the host distro gcc which means this error is very much likely to be from either your host system, or a hardware issue with that system. If you restart the build does it fail in the same way or does it move further? If it fails the same way its likely to be some host system issue. If it fails in a different way its likely a hardware issue like a memory problem. FWIW we test on Ubuntu 16.04 so that is a distro which is known to work.
Also note this is sumo which is now out of support
Since this release is no longer supported we're closing this here. As mentioned previously this does seem unlikely to be OE-Core related, its more likely to be the host distro, the hardware being used or perhaps the fsl layers which are being included. You may find people able to help on the mailing list if you're still stuck.