Re: Problem with libdrm.inc or eudev_%.bbappend

[Elias Diem <lists@webconect.ch>]

Hi Denys

On 2016-04-10, Denys Dmytriyenko wrote:

>On Sun, Apr 10, 2016 at 07:01:38PM +0200, Elias Diem wrote:
>> Hi
>>
>> I'm trying to build a layer[1] and experience some problems.
>>
>> Steps to reproduce:
>>
>> - I source `oe-init-build-env` like this:
>>  $ . /path/to/oe-init-build-env builddir
>>
>> - Then inside builddir, I change the two files `local.conf`  and
>> `bblayers.conf`. These two files are attached.
>>
>> - Then I start bitbake as follows:
>>
>>  $ bitbake mume-image
>>
>>  This will produce the following warning:
>>
>>  WARNING: Host distribution "Gentoo" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
>>
>>  And then it will produce the following error message:
>>
>>  ERROR: ParseError at /home/edi/var/yocto/meta-ti/recipes-graphics/drm/libdrm_2.4.41.bb:1: Could not include required file recipes-graphics/drm/libdrm.inc
>>
>>  The layer's README[2] tells me to use the branch `fido`  for
>> meta-ti. Apparently this branch does not contain a  file named
>> `libdrm.inc`.
>
>Well, and it shouldn't - in fido that file comes from oe-core. Looks like you
>are trying to mix/match different branches, which won't work. If you want
>fido, you have to use fido across the layers.

Thank you for your reply. This makes sense.

>> - I then change the meta-ti's branch to `master`. This  branch
>> contains the file `libdrm.inc`. I start bitbake  again:
>>
>>  $ bitbake mume-image
>>
>>  This will produce a new error:
>>
>>  ERROR: No recipes available for:
>>    /home/edi/var/yocto/meta-ti/recipes-core/udev/eudev_%.bbappend
>
>Two things - it was already fixed almost 2 weeks ago, so you seem to be using
>outdated snapshot. Second, use distro that doesn't error out on unused
>bbappends...
>
>And then again, you are trying to mix/match different branches of layers, so
>you might have some other weird issues down the road.

I use a workaround for now. I indeed mix the branches. But I 
delete the recipe `libdrm_2.4.41.bb` because I don't need 
libdrm.

Maybe I will find a nicer way to solve this problem in the 
future.

-- 
Greetings
Elias