imx8mm worrior build fails on busybox

cancel
Showing results for 
Search instead for 
Did you mean: 

imx8mm worrior build fails on busybox

254 Views
greeranjunk
Contributor II

hi

We are upgrading our BSP to the worrior on the imx8m-mini but when i build with fsl-image-qt5 the busybox fails.

 Value of CONFIG_SH_IS_NONE is redefined by fragment .config.app.suid:
| Previous value: # CONFIG_SH_IS_NONE is not set # CONFIG_SH_IS_NONE is not set # CONFIG_SH_IS_NONE is not set # CONFIG_SH_IS_NONE is not set # CONFIG_SH_IS_NONE is not set # CONFIG_SH_IS_NONE is not set # CONFIG_SH_IS_NONE is not set # CONFIG_SH_IS_NONE is not set # CONFIG_SH_IS_NONE is not set # CONFIG_SH_IS_NONE is not set
| New value: CONFIG_SH_IS_NONE=y CONFIG_SH_IS_NONE=y CONFIG_SH_IS_NONE=y CONFIG_SH_IS_NONE=y
|
| #
| # merged configuration written to .config (needs make)
| #
| NOTE: make -j 8 CC=aarch64-poky-linux-gcc  --sysroot=/home/bsp/yocto_builds/worrior/mini/var-fsl-yocto/build_mini_xwayland/tmp/work/aarch64-poky-linux/busybox/1.30.1-r0/recipe-sysroot LD=aarch64-poky-linux-gcc  --sysroot=/home/bsp/yocto_builds/worrior/mini/var-fsl-yocto/build_mini_xwayland/tmp/work/aarch64-poky-linux/busybox/1.30.1-r0/recipe-sysroot V=1 ARCH=aarch64 CROSS_COMPILE=aarch64-poky-linux- SKIP_STRIP=y HOSTCC=gcc  HOSTCPP=gcc  -E busybox_unstripped
| rm -f .kernelrelease
| /home/bsp/yocto_builds/worrior/mini/var-fsl-yocto/build_mini_xwayland/tmp/work/aarch64-poky-linux/busybox/1.30.1-r0/busybox-1.30.1/scripts/gen_build_files.sh /home/bsp/yocto_builds/worrior/mini/var-fsl-yocto/build_mini_xwayland/tmp/work/aarch64-poky-linux/busybox/1.30.1-r0/busybox-1.30.1 /home/bsp/yocto_builds/worrior/mini/var-fsl-yocto/build_mini_xwayland/tmp/work/aarch64-poky-linux/busybox/1.30.1-r0/busybox-1.30.1
| echo 1.30.1 > .kernelrelease
| make -f /home/bsp/yocto_builds/worrior/mini/var-fsl-yocto/build_mini_xwayland/tmp/work/aarch64-poky-linux/busybox/1.30.1-r0/busybox-1.30.1/Makefile silentoldconfig
| make -f scripts/Makefile.build obj=scripts/basic
| /home/bsp/yocto_builds/worrior/mini/var-fsl-yocto/build_mini_xwayland/tmp/work/aarch64-poky-linux/busybox/1.30.1-r0/busybox-1.30.1/scripts/gen_build_files.sh /home/bsp/yocto_builds/worrior/mini/var-fsl-yocto/build_mini_xwayland/tmp/work/aarch64-poky-linux/busybox/1.30.1-r0/busybox-1.30.1 /home/bsp/yocto_builds/worrior/mini/var-fsl-yocto/build_mini_xwayland/tmp/work/aarch64-poky-linux/busybox/1.30.1-r0/busybox-1.30.1
| mkdir -p include
| make -f scripts/Makefile.build obj=scripts/kconfig silentoldconfig
| scripts/kconfig/conf -s Config.in
| .config:1178:warning: trying to reassign symbol GUNZIP
| .config:1179:warning: trying to reassign symbol ZCAT
| .config:1180:warning: trying to reassign symbol FEATURE_GUNZIP_LONG_OPTIONS
| .config:1181:warning: trying to reassign symbol BUNZIP2
| .config:1182:warning: trying to reassign symbol BZCAT
| .config:2029:warning: trying to reassign symbol SH_IS_ASH
| .config:2030:warning: trying to reassign symbol ASH
| .config:2031:warning: trying to reassign symbol KLOGD
| .config:2032:warning: trying to reassign symbol FEATURE_KLOGD_KLOGCTL
| .config:2033:warning: trying to reassign symbol LOGGER
| .config:2034:warning: trying to reassign symbol LOGREAD
| .config:2035:warning: trying to reassign symbol FEATURE_LOGREAD_REDUCED_LOCKING
| .config:2036:warning: trying to reassign symbol SYSLOGD
| .config:2037:warning: trying to reassign symbol FEATURE_SYSLOGD_DUP
| .config:2038:warning: trying to reassign symbol FEATURE_SYSLOGD_CFG
| .config:2048:warning: trying to reassign symbol SH_IS_NONE
| .config:2048:warning: SH_IS_NONE creates inconsistent choice state
| .config:2049:warning: trying to reassign symbol SH_IS_NONE
| .config:2049:warning: SH_IS_NONE creates inconsistent choice state
| .config:2050:warning: trying to reassign symbol SH_IS_NONE
| .config:2050:warning: SH_IS_NONE creates inconsistent choice state
| #
| # using defaults found in .config
| #
| *
| * Restart config...
| *
| *
| * Shells
| *
| Choose which shell is aliased to 'sh' name
|   1. ash (SH_IS_ASH)
|   2. hush (SH_IS_HUSH)
| > 3. none (SH_IS_NONE)
| choice[1-3?]: aborted!
|
| Console input/output is redirected. Run 'make oldconfig' to update configuration.
|
| /home/bsp/yocto_builds/worrior/mini/var-fsl-yocto/build_mini_xwayland/tmp/work/aarch64-poky-linux/busybox/1.30.1-r0/busybox-1.30.1/scripts/kconfig/Makefile:40: recipe for target 'silentoldconfig' failed
| make[2]: *** [silentoldconfig] Error 1
| ERROR: oe_runmake failed
| /home/bsp/yocto_builds/worrior/mini/var-fsl-yocto/build_mini_xwayland/tmp/work/aarch64-poky-linux/busybox/1.30.1-r0/busybox-1.30.1/Makefile:444: recipe for target 'silentoldconfig' failed
| make[1]: *** [silentoldconfig] Error 2
| Makefile:523: recipe for target 'include/autoconf.h' failed
| make: *** [include/autoconf.h] Error 2
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /home/bsp/yocto_builds/worrior/mini/var-fsl-yocto/build_mini_xwayland/tmp/work/aarch64-poky-linux/busybox/1.30.1-r0/temp/log.do_compile.29360)
ERROR: Task (/home/bsp/yocto_builds/worrior/mini/var-fsl-yocto/sources/poky/meta/recipes-core/busybox/busybox_1.30.1.bb:do_compile) failed with exit code '1'

Second Keyboard Interrupt, stopping...

NOTE: Sending SIGTERM to remaining 4 tasks

Summary: 1 task failed:
  /home/bsp/yocto_builds/worrior/mini/var-fsl-yocto/sources/poky/meta/recipes-core/busybox/busybox_1.30.1.bb:do_compile
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

2 Replies

181 Views
greeranjunk
Contributor II

Thanks for the reply and sorry for not been in contact lately. The error was my fault and i did not see it in time. i got a machine with a small ram and it cause unpredictable problems. i added ram and all works well

thansk

181 Views
gusarambula
NXP TechSupport
NXP TechSupport

Hello Ran Gree,

Would you please confirm which BSP version and board you are using? From the log you are using a Variscite Yocto BSP, which is meant to support their boards. Variscite’s boards are manufactured and supported by them so they would be able to provide better guidance, and they have good resources on their wiki.

My apologies for the inconvenience!

Regards,

0 Kudos