[yocto] '…bzImage': No such file or directory when building core-image-minimal-initramfs

[Jeffrey Moore]

Hi Richard.  Thank you for the response.  This is with the Edison release.  I even pulled down a fresh copy to doubly make sure I didn't inadvertently corrupt any thing.  I've been building all different types of images with no problem at all.  This image type of "minimal-initramfs" is the only problem that I have encountered.  I am using Ubuntu 11.10 32 bit for my host but that is probably immaterial.

Jeff



On Nov 20, 2011, at 5:32 AM, Richard Purdie <richard.purdie at linuxfoundation.org> wrote:

> On Sat, 2011-11-19 at 16:20 -0500, Jeffrey Moore wrote:
>> I have a problem in  that the kernel bzImage is apparently not being
>> built.  Here is my error:
>> | install: cannot stat
>> `/media/jwm/minimal-initramfs/tmp/sysroots/crownbay-noemgd/kernel/bzImage': No such file or directory
>> | ERROR: Function 'build_boot_bin' failed
>> (see /media/jwm/minimal-initramfs/tmp/work/crownbay_noemgd-poky-linux/core-image-minimal-initramfs-1.0-r0/temp/log.do_bootimg.25097 for further information)
>> NOTE: package core-image-minimal-initramfs-1.0-r0: task do_bootimg:
>> Failed
>> ERROR: Task 9
>> (/home/jeff/poky-edison-6.0/meta/recipes-core/images/core-image-minimal-initramfs.bb, do_bootimg) failed with exit code '1'
>> ERROR:
>> '/home/jeff/poky-edison-6.0/meta/recipes-core/images/core-image-minimal-initramfs.bb' failed
>> 
>> My setup:
>> 
>> vanilla, out of the box poky setup with the addition of:
>> 
>> meta-intel layer for meta-crownbay  in the bblayers.conf 
>> & 
>> MACHINE ?= "crownbay-noemgd" in the local.conf
>> 
>> bitbake -k core-image-minimal-initramfs
>> 
>> If I build any other type of image such
>> as: core-image-minimal-mtdutils or core-image-minimal, everything is
>> fine and I get a clean build.  Any help would be appreciated.
> 
> I'm chasing a bug that looks very like this at the moment. I don't have
> a proper fix for it yet but you could try and "bitbake linux-yocto -c
> populate_sysroot -f" and then try and build your image again which
> should work around the problem.
> 
> I'm assuming this is with master rather than the release and you might
> have rm_work enabled?
> 
> Cheers,
> 
> Richard
> 
>