On 2/26/20 2:13 PM, Greg Wilson-Lindberg wrote:
-----Original Message-----
From: Khem Raj <[email protected]>
Sent: Wednesday, February 26, 2020 1:36 PM
To: Greg Wilson-Lindberg <[email protected]>; Yocto list discussion
<[email protected]>
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 <[email protected]>
Sent: Wednesday, February 26, 2020 12:30 PM
To: Greg Wilson-Lindberg <[email protected]>; Yocto list
discussion <[email protected]>
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








-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48628): https://lists.yoctoproject.org/g/yocto/message/48628
Mute This Topic: https://lists.yoctoproject.org/mt/71572710/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to