Hi everyone,
I have a working root fs based on "dizzy", for which I created a customized
machine config, a custom package config recipe and a custom image recipe.
When running into problems with the python installation on that rootfs I
decided to upgrade to Poky 1.8 "fido".
So I checked out the
> Hmmm. It shouldn't have gone missing. Bits of the kernel build outputs
> did move around in 1.8, but the abiversion is still generated and
> placed in the STAGING_KERNEL_BUILDDIR.
I was just wondering, is there an easy way to resolve these Paths from the
command line? I do not have a lot of e
> Have you tried setting linux-dummy as the preferred provider for the kernel
> ? That would skip the build processing doing anything more than satisfying
> the various kernel dependencies.
Ah, that's a good hint, I'll try that.
> >
> >> After your build has failed, if you look in STAGING_KERNEL_
> That is really odd. I'll be interested to hear how that happened. I just did a
> test and it points to where I expect:
>
> [/home/bruc...poky/build]> bitbake -e core-image-minimal | grep
> STAGING_KERNEL_BUILDDIR # $STAGING_KERNEL_BUILDDIR
> STAGING_KERNEL_BUILDDIR="/home/bruce/poky/build/tmp/
> What kernel recipe is used when your machine is set to 'astro' ?
> Something custom ? Or have you added machine compatibility to another
> known kernel recipe ?
How would I see which kernel recipe is used?
I did not customize anything except for aforementioned steps, simply copied
beaglebone.c
