All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Greg Wilson-Lindberg" <gwilson@sakuraus.com>
To: Yocto list discussion <yocto@yoctoproject.org>
Subject: Help with how to debug dependency error
Date: Wed, 26 Feb 2020 20:02:46 +0000	[thread overview]
Message-ID: <a701f94801884187afdd869e5a1b5420@sakuraus.com> (raw)

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?

Thanks in advance,
Greg Wilson-Lindberg

    

             reply	other threads:[~2020-02-26 20:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-26 20:02 Greg Wilson-Lindberg [this message]
2020-02-26 20:30 ` [yocto] Help with how to debug dependency error 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

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=a701f94801884187afdd869e5a1b5420@sakuraus.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.