From: Oliver Graute <oliver.graute@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: create_image.wic is missing u-boot SPL file
Date: Wed, 10 Feb 2016 17:14:58 +0100 [thread overview]
Message-ID: <20160210161458.GB27824@graute-opti> (raw)
Hello list,
I observe a problem with the create_image.wic script after second execution of
bitbake fsl-image
NOTE: recipe fsl-image-1.0-r0: task do_rootfs: Started
2016-02-10T03:21:41.323Z: ERROR: Error: The image creation script '/home/dnt/build-imx6ulevk/tmp/work/imx6ulevk-poky-linux-gnueabi/fsl-image/1.0-r0/temp/create_image.wic' returned 1:
2016-02-10T03:21:41.323Z: Error: exec_cmd: du -Lbks /home/dnt/build-imx6ulevk/tmp/deploy/images/imx6ulevk/SPL returned '1' instead of 0
2016-02-10T03:21:41.323Z: Checking basic build environment...
2016-02-10T03:21:41.323Z: Done.
2016-02-10T03:21:41.324Z:
2016-02-10T03:21:41.324Z: Creating image(s)...
2016-02-10T03:21:41.324Z:
2016-02-10T03:21:41.324Z: WARNING: exit code 1 from a shell command.
2016-02-10T03:21:41.324Z:
2016-02-10T03:21:41.324Z: ERROR: Function failed: do_rootfs
2016-02-10T03:21:41.371Z: ERROR: Logfile of failure stored in: /home/dnt/build-imx6ulevk/tmp/work/imx6ulevk-poky-linux-gnueabi/fsl-image/1.0-r0/temp/log.do_rootfs.27900
Somewhere the SPL symbolic link and the SPL files itself are deleted from my
deploy image folder during the wic run.
If i execute
bitbake -c cleansstate u-boot fsl-image
bitbake u-boot fsl-image
everything works fine, until I run next time bitbake fsl_image again
(without u-boot before)
Some ideas how to fix this?
Best regards,
Oliver
next reply other threads:[~2016-02-10 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 16:14 Oliver Graute [this message]
2016-02-11 6:38 ` create_image.wic is missing u-boot SPL file Ed Bartosh
2016-02-11 9:45 ` Oliver Graute
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=20160210161458.GB27824@graute-opti \
--to=oliver.graute@gmail.com \
--cc=openembedded-core@lists.openembedded.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