Re: Build fails moving from 4.0.1 to 5.0.1

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Fri, 2011-08-19 at 21:58 +0100, Chris Tapp wrote:
> On 19 Aug 2011, at 21:49, Richard Purdie wrote:
> 
> > On Fri, 2011-08-19 at 20:43 +0100, Chris Tapp wrote:
> >> On 19 Aug 2011, at 17:16, Richard Purdie wrote:
> >>
> >>> On Fri, 2011-08-19 at 08:29 +0100, Chris Tapp wrote:
> >>>> I've got a configuration that builds ok under 4.0.1, but when I  
> >>>> build
> >>>> under 5.0.1 I get the following right at the end:
> >>>>
> >>>> Installing task-poky-boot (1.0-r7) to root...
> >>>> Downloading file:/home/chris/yocto/ebox3300-build/tmp/deploy/ipk/
> >>>> Vortex86DX/task-poky-boot_1.0-r7_Vortex86DX.ipk.
> >>>> Installing task-sjs (1.0-r0) to root...
> >>>> Downloading file:/home/chris/yocto/ebox3300-build/tmp/deploy/ipk/
> >>>> Vortex86DX/task-sjs_1.0-r0_Vortex86DX.ipk.
> >>>> Unknown package 'run-postinsts'.
> >>>> Collected errors:
> >>>> * satisfy_dependencies_for: Cannot satisfy the following
> >>>> dependencies for task-poky-boot:
> >>>> * 	tinylogin * 	busybox * 	modutils-initscripts * 	initscripts * 	
> >>>> console-tools * 	initscripts * 	udev * 	sysvinit * 	netbase * 	 
> >>>> base-
> >>>> passwd *
> >>>> * opkg_install_cmd: Cannot install package task-poky-boot.
> >>>> * satisfy_dependencies_for: Cannot satisfy the following
> >>>> dependencies for task-sjs:
> >>>> * 	yocto-wallboard * 	psplash * 	syslinux *
> >>>> * opkg_install_cmd: Cannot install package task-sjs.
> >>>> * opkg_install_cmd: Cannot install package run-postinsts.
> >>>> ERROR: Function 'do_rootfs' failed (see ...
> >>>>
> >>>> If I look in tmp/work, it looks as if the missing dependencies have
> >>>> all been built and packaged within their work areas.
> >>>>
> >>>> I tried cleaning and rebuilding 'task-sjs', but that made no
> >>>> difference to the errors reported against it.
> >>>>
> >>>> Where should I start looking to work out what's going wrong here?  
> >>>> Is
> >>>> it as simple as needing to add something like RDEPENDS?
> >>>
> >>> This sounds like the machine specific packages are failing to be  
> >>> found
> >>> so it sounds like a package feed issue. Is sounds like PACKAGE_ARCHS
> >>> isn't listing everything it needs to (such as the machine name) or  
> >>> the
> >>> package system isn't finding a group of packages for some other
> >>> reason.
> >>
> >> Thanks, but that's way over my head at the moment ;-)
> >>
> >> I've searched through the meta data for PACKAGE_ARCHS, but that's not
> >> thrown anything up to make me think there was anything I should  
> >> look at.
> >>
> >> I'm using my own machine recipe. Is this were I should be looking?
> >
> > Yes, I suspect something about your machine config is resulting in  
> > this
> > but its hard to me to say what.
> >
> > You can do things like "bitbake -e | grep ^PACKAGE_ARCHS" to see the
> > contents of variables. I'm curious if your machine name is listed in
> > that list.
> 
> chris@ubuntu:~/yocto/ebox3300-build$ bitbake -e |grep "PACKAGE_ARCHS"
> 
> # PACKAGE_ARCHS=all any noarch ${PACKAGE_EXTRA_ARCHS} ${MACHINE_ARCH}
> PACKAGE_ARCHS="all any noarch x86 Vortex86DX"
> 		ipkg_archs = bb.data.getVar('PACKAGE_ARCHS',d)
> 			bb.error("PACKAGE_ARCHS missing")
> 
> My machine is "Vortex86DX"

What does "ls /home/chris/yocto/ebox3300-build/tmp/deploy/ipk" say?

Cheers,

Richard