All of lore.kernel.org
 help / color / mirror / Atom feed
From: randy <randy.krakora@freescale.com>
To: <meta-freescale@yoctoproject.org>
Subject: bitbake debug
Date: Thu, 11 Dec 2014 08:57:09 -0500	[thread overview]
Message-ID: <5489A2B5.5090800@freescale.com> (raw)
In-Reply-To: <1418265361-31173-2-git-send-email-alfonso@tames.com>

Hello,

Is there a bitbake command to list the variables for a specific recipe ( 
like what is the value of PREFERRED_PROVIDER_virtual/libgl, etc. )? Also 
is there a command to output package depenencies? Like for the following 
error:

ERROR: Trying to resolve runtime dependency libgles2 resulted in 
conflicting PREFERRED_PROVIDER entries being found.
The providers found were: 
['/home/rfkrakora/freescale/yocto/yocto_3.10.17-1.0.2/sources/meta-fsl-bsp-release/imx/meta-fsl-arm/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q_3.10.17-1.0.2-hfp.bb', 
'/home/rfkrakora/freescale/yocto/yocto_3.10.17-1.0.2/sources/poky/meta/recipes-graphics/mesa/mesa_9.1.6.bb']
The PREFERRED_PROVIDER entries resulting in this conflict were: 
['PREFERRED_PROVIDER_virtual/libgl = gpu-viv-bin-mx6q', 
'PREFERRED_PROVIDER_virtual/mesa = mesa']

I'd imagine if I could see the dependencies, there would be one in 
question because of this conflict?

-Randy Krakora



  reply	other threads:[~2014-12-11 14:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11  2:36 [meta-fsl-arm-extra][PATCH v2 1/2] wandboard: Add Alfonso Tames as maintainer Alfonso Tames
2014-12-11  2:36 ` [meta-fsl-arm-extra][PATCH v2 2/2] linux-wandboard: Update to 3.10.31-1.1.0 beta2 based kernel Alfonso Tames
2014-12-11 13:57   ` randy [this message]
2014-12-11 14:38     ` bitbake debug Gary Thomas
2014-12-11 21:53 ` [meta-fsl-arm-extra][PATCH v2 1/2] wandboard: Add Alfonso Tames as maintainer John Weber
2014-12-12 22:25   ` Alfonso Tamés

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=5489A2B5.5090800@freescale.com \
    --to=randy.krakora@freescale.com \
    --cc=meta-freescale@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.