Build Configuration: BB_VERSION = "1.21.1" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Fedora-19" TARGET_SYS = "x86_64-poky-linux" MACHINE = "nuc" DISTRO = "poky" DISTRO_VERSION = "1.5+snapshot-20140205" TUNE_FEATURES = "m64 corei7" TARGET_FPU = "" meta meta-yocto meta-yocto-bsp = "master:4e9eb77108c7e628ebd00ec848b8bc034802e197" meta-intel meta-nuc = "master:c5ca9f67121bff0b7400a175f005212234906b37" At this moment, we have piglit added by default to the sato-sdk image. Adding IMAGE_INSTALL_append = " piglit" to the local.conf and building a sato image (or sato-sdk) results in image not being installed on BSP. The following message is presented after answering to the installation location/storage question: *********************************** Installing image on /dev/sda ... cat: write error: Invalid argument Installation image failed sh: cannot set terminal process group(-1): Inappropriate ioctl for device sh: no job control in this shell *********************************** The piglit testsuite can be successfully run in live boot.
Created attachment 1759 [details] pn-buildlist files The pn-buildlist files are from both scenarios(with/without piglit appended) to a sato-sdk image for nuc
The package list is identical, so there must be a difference in the rootfs.
Please use CORE_IMAGE_EXTRA_INSTALL instead of IMAGE_INSTALL
That worked fine although it's just a workaround. Thanks
You point out an interesting issue with the usage of IMAGE_INSTALL to generally add things to the image vs using CORE_IMAGE_EXTRA_INSTALL. Since you don't like CORE_IMAGE_EXTRA_INSTALL and since adding a package to IMAGE_INSTALL affects both the image you are building and the initramfs image, another option is to add an explict IMAGE_INSTALL_append_pn-<image name> = " <package names>"to your local.conf this will cause that set of packages in <package names> to only be installed in that particular image that you define in <image name>. The other option is we change IMAGE_INSTALL's meaning somehow for the initramfs image specificly so that it can not be appended to, but I don't think that's the right solution either.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=8d13b43f16ea289afc93f14d5dfbff5d81520a01
I could successfully install the image after the mentioned commit.
Somehow I changed the status. Changing it back to Resolved/Fixed
Setting to Verified as per Comment #7 Sorry for the missunderstanding
Hi, For the documentation component for this fixed bug, it seems like I need to expand on the definitions of IMAGE_INSTALL and CORE_IMAGE_EXTRA_INSTALL, both of which we have in our glossary (http://www.yoctoproject.org/docs/1.6/ref-manual/ref-manual.html#var-IMAGE_INSTALL and http://www.yoctoproject.org/docs/1.6/ref-manual/ref-manual.html#var-CORE_IMAGE_EXTRA_INSTALL. Would providing the general information that Saul points out in Comment 5 cover this well enough? Thanks, Scott