From: "Patrick Davis" <p.davis@astronautics.com>
To: "meta-freescale@lists.yoctoproject.org"
<meta-freescale@lists.yoctoproject.org>
Subject: Issues with make_dtb_boot_files
Date: Wed, 26 Feb 2020 19:53:25 +0000 [thread overview]
Message-ID: <05845666ca3b4f8bbe7f533eebd3b135@HQ-EX2013A.aca.astronautics.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4204 bytes --]
I'm running into a rather odd issue when attempting to upgrade a custom target (machine and distro) based off of the iMX6 platform from Thud to Warrior. (The build works just fine in Thud.) The build for warrior fails at do_image_wic because it cannot execute make_dtb_boot_files. More specifically, it expects make_dtb_boot_files to be a file and then fails when it can't find the file. Here is build output:
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_image_wic
| INFO: Creating image(s)...
|
| ERROR: _exec_cmd: install -m 0644 -D /home/vagrant/warrior/build/tmp/deploy/images/custom /make_dtb_boot_files /home/vagrant/warrior/build/tmp/work/custom-custom-linux-gnueabi/rootfs/1.0-r0/deploy-rootfs-image-complete/rootfs-custom-20200226170413/tmp.wic.a1r6y7th/boot.2/make_dtb_boot_files returned '1' instead of 0
| output: install: cannot stat '/home/vagrant/warrior/build/tmp/deploy/images/custom/make_dtb_boot_files': No such file or directory
|
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_image_wic (log file is located at /home/vagrant/warrior/build/tmp/work/custom-custom-linux-gnueabi/rootfs/1.0-r0/temp/log.do_image_wic.764)
ERROR: Task (/home/vagrant/warrior/sources/meta-custom-bsp/recipes-aca/images/rootfs.bb:do_image_wic) failed with exit code '1'
Note, "rootfs" is the build target in question.
As part of my own investigation into this issue, I believe this issue stems from the rootfs.env file incorrectly being compiled. If I open the 'rootfs.env' file located within build/tmp/sysroots/custom/imgdata, I find the following:
BBLAYERS="/home/vagrant/warrior/sources/poky/meta /home/vagrant/warrior/sources/poky/meta-poky /home/vagrant/warrior/sources/meta-openembedded/meta-oe /home/vagrant/warrior/sources/meta-openembedded/meta-multimedia /home/vagrant/warrior/sources/meta-freescale /home/vagrant/warrior/sources/meta-freescale-3rdparty /home/vagrant/warrior/sources/meta-freescale-distro /home/vagrant/warrior/sources/meta-fsl-bsp-release/imx/meta-bsp /home/vagrant/warrior/sources/meta-fsl-bsp-release/imx/meta-sdk /home/vagrant/warrior/sources/meta-fsl-bsp-release/imx/meta-ml /home/vagrant/warrior/sources/meta-browser /home/vagrant/warrior/sources/meta-rust /home/vagrant/warrior/sources/meta-openembedded/meta-networking /home/vagrant/warrior/sources/meta-openembedded/meta-python /home/vagrant/warrior/sources/meta-openembedded/meta-filesystems /home/vagrant/warrior/sources/meta-qt5 /home/vagrant/warrior/sources/meta-custom-bsp /home/vagrant/warrior/sources/meta-mender/meta-mender-core"
IMGDEPLOYDIR="/home/vagrant/warrior/build/tmp/work/custom-custom-linux-gnueabi/rootfs/1.0-r0/deploy-rootfs-image-complete"
DEPLOY_DIR_IMAGE="/home/vagrant/warrior/build/tmp/deploy/images/custom"
FAKEROOTCMD="/home/vagrant/warrior/build/tmp/sysroots-components/x86_64/pseudo-native/usr/bin/pseudo"
IMAGE_BASENAME="rootfs"
IMAGE_BOOT_FILES="zImage ${@make_dtb_boot_files(d)} ${@bb.utils.contains('COMBINED_FEATURES<mailto:$%7b@bb.utils.contains('COMBINED_FEATURES>', 'optee', 'tee.bin uTee-${OPTEE_BIN_EXT}', '', d)} ${@bb.utils.contains('COMBINED_FEATURES<mailto:$%7b@bb.utils.contains('COMBINED_FEATURES>', 'xen', 'xen', '', d)}"
IMAGE_LINK_NAME="rootfs-custom"
IMAGE_ROOTFS="/home/vagrant/warrior/build/tmp/work/custom-custom-linux-gnueabi/rootfs/1.0-r0/rootfs"
INITRAMFS_FSTYPES="cpio.gz"
RECIPE_SYSROOT_NATIVE="/home/vagrant/warrior/build/tmp/work/custom-custom-linux-gnueabi/rootfs/1.0-r0/recipe-sysroot-native"
ROOTFS_SIZE="121498"
STAGING_DATADIR="/home/vagrant/warrior/build/tmp/work/custom-custom-linux-gnueabi/rootfs/1.0-r0/recipe-sysroot/usr/share"
STAGING_DIR="/home/vagrant/warrior/build/tmp/sysroots"
STAGING_LIBDIR="/home/vagrant/warrior/build/tmp/work/custom-custom-linux-gnueabi/rootfs/1.0-r0/recipe-sysroot/usr/lib"
TARGET_SYS="arm-custom-linux-gnueabi"
The problem is, I have no idea what my custom layer/build target would have done to interfere with the creation of the rootfs.env file, or how to go about fixing it. Any help or guidance that can be offered would be greatly appreciated.
Thank you.
-Patrick
[-- Attachment #2: Type: text/html, Size: 7558 bytes --]
reply other threads:[~2020-02-26 19:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=05845666ca3b4f8bbe7f533eebd3b135@HQ-EX2013A.aca.astronautics.com \
--to=p.davis@astronautics.com \
--cc=meta-freescale@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).