Running '. ./oe-init-build-env; wic create directdisk -e core-image-sato -o ${BUILDDIR}/tmp/deploy/wic_images/qemux86-64/directdisk/core-image-sato/' with output to /srv/pokybuild/yocto-worker/wic/build/build/command-3-cmds.log
This is the default build configuration for the Poky reference distribution.
### Shell environment set up for builds. ###
You can now run 'bitbake <target>'
Common targets are:
core-image-minimal
core-image-full-cmdline
core-image-sato
core-image-weston
meta-toolchain
meta-ide-support
You can also run generated qemu images with a command like 'runqemu qemux86-64'.
Other commonly useful commands are:
- 'devtool' and 'recipetool' handle common recipe tasks
- 'bitbake-layers' handles common layer tasks
- 'oe-pkgdata-util' handles common target package tasks
ERROR: _exec_cmd: bitbake -e core-image-sato returned '1' instead of 0
output: NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 98 entries from dependency cache.
Parsing recipes...ERROR: /srv/pokybuild/yocto-worker/wic/build/meta/recipes-core/images/core-image-base.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'tar.zstd' - possibly invalid type name or missing support class
ERROR: /srv/pokybuild/yocto-worker/wic/build/meta/recipes-core/images/core-image-minimal-dev.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'tar.zstd' - possibly invalid type name or missing support class
ERROR: /srv/pokybuild/yocto-worker/wic/build/meta/recipes-core/images/core-image-minimal-mtdutils.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'tar.zstd' - possibly invalid type name or missing support class
ERROR: /srv/pokybuild/yocto-worker/wic/build/meta/recipes-core/images/core-image-minimal.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'tar.zstd' - possibly invalid type name or missing support class
ERROR: /srv/pokybuild/yocto-worker/wic/build/meta/recipes-core/images/core-image-ptest.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'tar.zstd' - possibly invalid type name or missing support class
ERROR: Parsing halted due to errors, see error messages above
Summary: There were 6 ERROR messages, returning a non-zero exit code.
Running '. ./oe-init-build-env; wic create directdisk-gpt -e core-image-sato -o ${BUILDDIR}/tmp/deploy/wic_images/qemux86-64/directdisk/core-image-sato/' with output to /srv/pokybuild/yocto-worker/wic/build/build/command-3-cmds.log
This is the default build configuration for the Poky reference distribution.
### Shell environment set up for builds. ###
You can now run 'bitbake <target>'
Common targets are:
core-image-minimal
core-image-full-cmdline
core-image-sato
core-image-weston
meta-toolchain
meta-ide-support
You can also run generated qemu images with a command like 'runqemu qemux86-64'.
Other commonly useful commands are:
- 'devtool' and 'recipetool' handle common recipe tasks
- 'bitbake-layers' handles common layer tasks
- 'oe-pkgdata-util' handles common target package tasks
ERROR: _exec_cmd: bitbake -e core-image-sato returned '1' instead of 0
output: NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 100 entries from dependency cache.
Parsing recipes...ERROR: /srv/pokybuild/yocto-worker/wic/build/meta/recipes-core/images/core-image-base.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'tar.zstd' - possibly invalid type name or missing support class
ERROR: /srv/pokybuild/yocto-worker/wic/build/meta/recipes-core/images/core-image-minimal-dev.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'tar.zstd' - possibly invalid type name or missing support class
ERROR: /srv/pokybuild/yocto-worker/wic/build/meta/recipes-core/images/core-image-minimal-mtdutils.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'tar.zstd' - possibly invalid type name or missing support class
ERROR: /srv/pokybuild/yocto-worker/wic/build/meta/recipes-core/images/core-image-minimal.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'tar.zstd' - possibly invalid type name or missing support class
ERROR: /srv/pokybuild/yocto-worker/wic/build/meta/recipes-core/images/core-image-ptest.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'tar.zstd' - possibly invalid type name or missing support class
ERROR: Parsing halted due to errors, see error messages above
Summary: There were 6 ERROR messages, returning a non-zero exit code.
