[yocto] some yocto/poky issues and errors

[Frans Meulenbroeks]

2010/11/3 Richard Purdie <rpurdie at linux.intel.com>:
> On Wed, 2010-11-03 at 09:27 +0100, Frans Meulenbroeks wrote:
ess it would be nice if bitbake would have given a decent error msg though.
>>
>> Frans (btw: still confused on the do_package thing)
>
> Can you point at a copy of this recipe or the do_package function? At
> this point its hard to guess what the problem might be. I suspect you
> might be right about there being a reference to but not a definition of
> a variable.

Richard, the recipe was a private kernel recipe which actually didn't
do too much.

It reads:

recipes/linux/linux-factory_2.6.34.bb:

FILESPATHPKG_append = ":linux-${PV}"

require linux_${PV}.bb

PACKAGES = ""
PROVIDES = ""
KERNEL_IMAGE_BASE_NAME = "${KERNEL_IMAGETYPE}-${PN}-${PV}-${PR}-${MACHINE}"
KERNEL_IMAGE_SYMLINK_NAME = "${KERNEL_IMAGETYPE}-${PN}-${MACHINE}"

S = "${WORKDIR}/linux-${PV}"

do_populate_sysroot() {
}

do_install() {
}

python do_package() {
}

As you see the do_package function is empty.
Basically this recipe was created as a mechanism (not necessarily the
best :-) ) to create a 2nd kernel for the same hardware which could be
used for factory upgrade. Idea is that this kernel has a much smaller
defconfig.

Actually I don't really know any more how/why I came to the code
above. I guess I just copied some stuff from oe kexecboot recipes. It
did what I needed it to do, so I just moved on to the next issue.
(and I must admit that I have no idea why the python thingie is there
before do_package, but I saw the same in a few other oe recipes).

Frans.