I was able to build core-image-base from Dylan with no problem. I then added
my own layer that specifies an RT kernel by including "linux-yocto-rt" in my
top-level recipe, and then setting PREFERRED_PROVIDER_virtual/kernel to
"linux-yocto-rt" in bblayers.conf. It complained that none of the available
kernel recipes (linux-yocto-rt_*) were compatible with my machine, because
they all set COMPATIBLE_MACHINE to a list of qemu machines, which isn't what
I'm building for. So I created a linux-yocto-rt_3.8.bbappend file that just
sets COMPATIBLE_MACHINE to what I'm building for, and now it's building
away.

My question is this: why was I able to build core-image base without
complaint in the first place? The kernel recipes it has available
(linux-yocto_*) also set COMPATIBLE_MACHINE to a list of qemu machines.

--

Ciao, Paul D. DeRocco
Paul mailto:pderocco@...

Hi Paul,

On 20/06/13 20:40, Paul D. DeRocco wrote:

My question is this: why was I able to build core-image base without
complaint in the first place? The kernel recipes it has available
(linux-yocto_*) also set COMPATIBLE_MACHINE to a list of qemu machines.

It probably built the linux-dummy recipe. An easy way to see which
recipe is being used is to run 'bitbake virtual/kernel'.

Tomas

--
http://sleepfive.com

From: Tomas Frydrych

On 20/06/13 20:40, Paul D. DeRocco wrote:

My question is this: why was I able to build core-image base without
complaint in the first place? The kernel recipes it has available
(linux-yocto_*) also set COMPATIBLE_MACHINE to a list of

qemu machines.

It probably built the linux-dummy recipe. An easy way to see which
recipe is being used is to run 'bitbake virtual/kernel'.

I'm not sure what linux-dummy is for, but given that it's full of empty
tasks, that looks like something that won't boot. But the resulting image
booted fine.

--

Ciao, Paul D. DeRocco
Paul mailto:pderocco@...