• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 535 subscribers
  • Views 515 views
  • Users 0 members are here
Options
Related

RZ/G2M Yocto Build Error: 'Nothing PROVIDES virtual/libgl'

Sid

Hello Experts,

I'm currently working on a Yocto project for the RZ/G2M board, specifically preparing the core-image-weston.

Using VLP v3.0.6

 I have also added the RZ MPU HTML5 (Gecko) Package for Verified Linux Packages [5.10-CIP] as per the user guide. During the build, I encountered the following error:

ERROR: Nothing PROVIDES 'virtual/libgl' (but /home/rzg-v3.0.6/build/../poky/meta/recipes-graphics/clutter/clutter-1.0_1.26.2.bb, /home/rzg-v3.0.6/build/../poky/meta/recipes-graphics/cairo/cairo_1.16.0.bb, /home/rzg-v3.0.6/build/../poky/meta/recipes-graphics/libepoxy/libepoxy_1.5.4.bb DEPENDS on or otherwise requires it)
mesa PROVIDES virtual/libgl but was skipped: PREFERRED_PROVIDER_virtual/libgbm set to libgbm, not mesa
ERROR: Nothing RPROVIDES 'libgl' (but /home/rzg-v3.0.6/build/../poky/meta/recipes-gnome/gtk+/gtk+3_3.24.14.bb, /home/rzg-v3.0.6/build/../poky/meta/recipes-graphics/cogl/cogl-1.0_1.22.4.bb RDEPENDS on or otherwise requires it)
ERROR: Required build target 'core-image-weston' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-weston', 'clutter-1.0-examples', 'gtk+3', 'libgl']

Here are the relevant parts of my local.conf:


# Enable Wayland and disable X11
DISTRO_FEATURES_append = " wayland x11"
#DISTRO_FEATURES_remove = " x11"
#IMAGE_FEATURES_append = " x11"
DISTRO_FEATURES_append = " virtualization"

# For Wayland/Weston
DISTRO_FEATURES_NATIVESDK_append = " wayland"
DISTRO_FEATURES_append = " pam"
PREFERRED_PROVIDER_virtual/libgles1 = ""
PREFERRED_PROVIDER_virtual/libgles2 = "gles-user-module"
PREFERRED_PROVIDER_virtual/egl = "libegl"
PREFERRED_PROVIDER_virtual/libgl = ""
PREFERRED_PROVIDER_virtual/mesa = ""
PREFERRED_PROVIDER_libgbm = "libgbm"
PREFERRED_PROVIDER_libgbm-dev = "libgbm"
BBMASK .= "|mesa-gl"

I've tried configuring the provider settings as shown above, but the build still fails with the errors.

Could anyone provide insights or suggestions on how to resolve this issue?

Specifically, I'm unsure if the PREFERRED_PROVIDER settings are correctly configured or if there's another step I should take to ensure the dependencies are properly met.