[poky] Build failure

[Tian, Kevin]

> From: Gary Thomas
> Sent: Tuesday, January 25, 2011 7:06 AM
> 
> On 01/24/2011 02:52 PM, Tom Zanussi wrote:
> > On Mon, 2011-01-24 at 13:36 -0800, Gary Thomas wrote:
> >> Trying to build poky-image-sato-live:
> >>     OE Build Configuration:
> >>     BB_VERSION        = "1.11.0"
> >>     METADATA_BRANCH   = "master"
> >>     METADATA_REVISION =
> "74783fec56d6ced1a793b36410233472e7daf445"
> >>     TARGET_ARCH       = "i586"
> >>     TARGET_OS         = "linux"
> >>     MACHINE           = "qemux86"
> >>     DISTRO            = "poky"
> >>     DISTRO_VERSION    = "0.9+snapshot-20110124"
> >>     TARGET_FPU        = ""
> >>
> >> ERROR: Function 'build_boot_bin' failed (see
> /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/te
> mp/log.do_bootimg.10954 for further information)
> >> ERROR:
> '/tmp/poky-amltd2/meta/recipes-sato/images/poky-image-sato-live.bb' failed
> >> ERROR: Logfile of failure stored in:
> /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/te
> mp/log.do_bootimg.10954
> >> Log data follows:
> >> | install: cannot stat
> `/home/local/pc_poky/tmp/sysroots/qemux86-poky-linux/kernel/bzImage': No
> such file or directory
> >> | Function 'build_boot_bin' failed (see
> /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/te
> mp/log.do_bootimg.10954 for further information)
> >> | ERROR: Function 'build_boot_bin' failed (see
> /home/local/pc_poky/tmp/work/i586-poky-linux/poky-image-sato-live-1.0-r0/te
> mp/log.do_bootimg.10954 for further information)
> >> NOTE: package poky-image-sato-live-1.0-r0: task build_boot_bin: Failed
> >> ERROR: Task 9
> (/tmp/poky-amltd2/meta/recipes-sato/images/poky-image-sato-live.bb,
> do_bootimg) failed with exit code '1'
> >>
> >> n.b. I tried to access BugZilla to report this, but that
> >> failed as well :-(
> >>
> >
> > The problem is this commit:
> >
> > commit bc9d2fbfd4eaad0df5647dd5d07dfb9fcff80ff3
> > Author: Dongxiao Xu<dongxiao.xu at intel.com>
> > Date:   Tue Jan 18 16:17:58 2011 +0800
> >
> >      staging: Use relative path in sysroot-destdir for target recipes
> >
> > Dongxiao is aware of the problem and working on a fix.  In the meantime,
> > you could try the fix below from Dongxiao, cut and pasted from IRC, or
> > back up to the commit before that...
> >
> > Hope that helps,
> >
> > Tom
> >
> > diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> > index 9d3b2bb..d1b5398 100644
> > --- a/meta/classes/kernel.bbclass
> > +++ b/meta/classes/kernel.bbclass
> > @@ -512,3 +512,5 @@ EXPORT_FUNCTIONS do_deploy
> > PACKAGES =+ "perf"
> > FILES_perf = "${bindir}/* \
> > ${libexecdir}"
> > +
> > +do_populate_sysroot[sstate-outputdirs] =
> "${STAGING_DIR}/${MACHINE}${HOST_VENDOR}-${HOST_OS}/"
> 
> Yes, this helped, but I did have to run 'bitbake virtual/kernel -c clean'
> before it made any difference.
> 
> Thanks

PR needs to be bumped in this case, which however reminds me one confusing area
I didn't think about before.

How do we handle the class changes which are inherited by many recipes? Generally
we need bump PRs once the output of a recipe gets changed, but it looks class file
is usually ignored.

Is there any easy way to have all recipes inheriting same class file bumping their PRs,
or has to be done by manual check?

Thanks
Kevin