[linux-yocto] about beaglebone-yocto bitbake core-image-rt

[Bruce Ashfield]

On 09/27/2018 02:15 AM, 劉家祿 wrote:
> $ git clone git://git.yoctoproject.org/poky
> $ cd poky
> $ . ./oe-init-build-env build-bbb
> 
> edit conf/local.conf to set MACHINE ??= "beaglebone-yocto"
> 
> $ echo "PREFERRED_PROVIDER_virtual/kernel = \"linux-yocto-rt\"" >> 
> conf/local.conf
> $ bitbake -v core-image-rt
> 
> got errors:
> 
> Loading cache...done.
> Loaded 1260 entries from dependency cache.
> NOTE: Resolving any missing task queue dependencies
> NOTE: selecting pseudo-native to satisfy virtual/fakeroot-native due to 
> PREFERRED_PROVIDERS
> ERROR: Nothing PROVIDES 'linux-yocto-rt' (but 
> /home/jaloo/backup/yocto/src/poky/meta/recipes-rt/images/core-image-rt.bb DEPENDS 
> on or otherwise requires it)
> linux-yocto-rt was skipped: incompatible with machine beaglebone-yocto 
> (not in COMPATIBLE_MACHINE)
> linux-yocto-rt was skipped: incompatible with machine beaglebone-yocto 
> (not in COMPATIBLE_MACHINE)
> NOTE: Target 'linux-yocto-rt' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['linux-yocto-rt']
> NOTE: Target 'core-image-rt' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['core-image-rt', 
> 'linux-yocto-rt']
> ERROR: Required build target 'core-image-rt' has no buildable providers.
> Missing or unbuildable dependency chain was: ['core-image-rt', 
> 'linux-yocto-rt']

The problem is just what they error message is trying to say.
There's no declared machine compatibility between that board
and the linux-yocto-rt recipe.

You could create a bbappend that contained both a BSP
definition and that sets the compatibility. But I can't
say if it would, or wouldn't have runtime issues.

i.e. you need to append beaglbone-yocto to the COMPATIBLE_MACHINE
variable.

You also need a BSP definition for the -rt kernel, but at
a glance, it looks like there's already one in the kernel-cache,
so you should get a valid configuration.

Bruce

> 
> Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
> 
> 
> 
> 
>