From: "Khem Raj" <raj.khem@gmail.com>
To: Greg Wilson-Lindberg <GWilson@sakuraus.com>,
Yocto list discussion <yocto@yoctoproject.org>
Subject: Re: [yocto] Help with how to debug dependency error
Date: Wed, 26 Feb 2020 14:16:35 -0800 [thread overview]
Message-ID: <b91e8e37-41be-e2c4-593a-ba42a4fdb602@gmail.com> (raw)
In-Reply-To: <77c8c143f7f74e699221ff73e8598d8c@sakuraus.com>
On 2/26/20 2:13 PM, Greg Wilson-Lindberg wrote:
>> -----Original Message-----
>> From: Khem Raj <raj.khem@gmail.com>
>> Sent: Wednesday, February 26, 2020 1:36 PM
>> To: Greg Wilson-Lindberg <GWilson@sakuraus.com>; Yocto list discussion
>> <yocto@yoctoproject.org>
>> Subject: Re: [yocto] Help with how to debug dependency error
>>
>>
>>
>> On 2/26/20 1:16 PM, Greg Wilson-Lindberg wrote:
>>> Hi Khem,
>>>
>>> Thanks for the (possible) solution. What I was really looking for is
>>> some way of finding out what changed with the addition of the OSTree
>>> directories that then caused the need for the additional libraries.
>>> Are there some tools that I don't know about that will help me find
>>> what is causing the gbm & gles2 to now be included when they are not
>> necessary without the OSTree dirs.
>>
>> bitbake -g would give you the dependency graph which you can use to find
>> out.
>
> As I said in the original post, bitbake errors out before it generates the dependency graph.
>
> This is why I was asking if there are other tools that could help.
ah I missed that right. I guess, parsing errors are your best bet then
>
>>>
>>> Regards,
>>> Greg
>>>
>>>> -----Original Message-----
>>>> From: Khem Raj <raj.khem@gmail.com>
>>>> Sent: Wednesday, February 26, 2020 12:30 PM
>>>> To: Greg Wilson-Lindberg <GWilson@sakuraus.com>; Yocto list
>>>> discussion <yocto@yoctoproject.org>
>>>> Subject: Re: [yocto] Help with how to debug dependency error
>>>>
>>>>
>>>>
>>>> On 2/26/20 12:02 PM, Greg Wilson-Lindberg wrote:
>>>>> I am building a system based on a boot2qt warrior Yocto build for
>>>>> the
>>>> Raspberry Pi4.
>>>>>
>>>>> Our system is building just fine until I try to add support for
>>>>> OSTree. When I
>>>> do that I get 3 errors for existing recipes, "nothing provides
>>>> virtual/gbm", "nothing provides virtual/egl", and "nothing provides
>>>> virtual/gles2". All of these are specified in PACKAGECONFIG[] lines
>>>> in qtbase_git.bb as required when gbm and gles2 are turned on.
>>>>>
>>>>> I have searched for gbm in the meta-updater &
>>>>> meta-updater-raspberrypi
>>>> directories that get included to add support for OSTree and found no
>>>> reference. It looks like the OSTree inclusion is requesting something
>>>> that is in turn requesting gbm and gles2 but I haven't been able to
>>>> figure out what that is.
>>>>>
>>>>> I have tried to print out the variables and a dependency graph to
>>>>> help me
>>>> track down what is going wrong, but these don't work because the
>>>> errors abort before I can get the information I need out.
>>>>>
>>>>> Can anyone point me to a way to find out what is triggering the
>>>>> change in
>>>> the gbm & gles2 packages?
>>>>>
>>>>
>>>> this is meta-rpi issue, perhaps you can use mesa there instead of
>>>> userland graphics driver
>>>>
>>>> MACHINE_FEATURES_append_rpi = " vc4graphics"
>>>>
>>>>
>>>>
>>>>> Thanks in advance,
>>>>> Greg Wilson-Lindberg
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
prev parent reply other threads:[~2020-02-26 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 20:02 Help with how to debug dependency error Greg Wilson-Lindberg
2020-02-26 20:30 ` [yocto] " Khem Raj
2020-02-26 21:16 ` Greg Wilson-Lindberg
2020-02-26 21:36 ` Khem Raj
2020-02-26 22:13 ` Greg Wilson-Lindberg
2020-02-26 22:16 ` Khem Raj [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b91e8e37-41be-e2c4-593a-ba42a4fdb602@gmail.com \
--to=raj.khem@gmail.com \
--cc=GWilson@sakuraus.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox