No package 'gbm' found

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

No package 'gbm' found

5,622 Views
jmariathas
Contributor I

Is there any common way to fix No package 'gbm' found error.

Log data follows:
| DEBUG: Executing shell function do_configure
| ERROR at //build/config/linux/pkg_config.gni:103:17: Script returned non-zero exit code.
|     pkgresult = exec_script(pkg_config_script, args, "value")
|                 ^----------
| Current dir: /mnt/hd/yocto-2.5/build/tmp/work/armv7at2hf-neon-mx6qdl-fslc-linux-gnueabi/chromium-ozone-wayland/71.0.3545.0.r589108.igalia.1-r0/chromium-ozone-wayland-dev-71.0.3545.0.r589108.igalia.1/out/Release/
| Command: python /mnt/hd/yocto-2.5/build/tmp/work/armv7at2hf-neon-mx6qdl-fslc-linux-gnueabi/chromium-ozone-wayland/71.0.3545.0.r589108.igalia.1-r0/chromium-ozone-wayland-dev-71.0.3545.0.r589108.igalia.1/build/config/linux/pkg-config.py gbm
| Returned 1.
| stderr:
|
| Package gbm was not found in the pkg-config search path.
| Perhaps you should add the directory containing `gbm.pc'
| to the PKG_CONFIG_PATH environment variable
| No package 'gbm' found
| Could not run pkg-config.
|
| See //third_party/minigbm/BUILD.gn:120:3: whence it was called.
|   pkg_config("libgbm") {
|   ^---------------------
| See //ui/ozone/platform/wayland/BUILD.gn:92:5: which caused the file to be included.
|     "//third_party/minigbm",
|     ^----------------------
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_configure (log file is located at /mnt/hd/yocto-2.5/build/tmp/work/armv7at2hf-neon-mx6qdl-fslc-linux-gnueabi/chromium-ozone-wayland/71.0.3545.0.r589108.igalia.1-r0/temp/log.do_configure.16718)

0 Kudos
3 Replies

4,486 Views
ruchika_dahiya
Contributor I

Any recommended Solution find for this problem . 

I am facing the same error log .

Regards,

0 Kudos

4,486 Views
gusarambula
NXP TechSupport
NXP TechSupport

Hello Jmariathas,

This error usually refers to an unmet dependency.

You could add this package (provided that it is available on the Yocto build directory you have initialized) using the DEPENDS variable on the recipe:

DEPENDS += “gmb”

However, I have not tested the chromium recipe. Which BSP are you using?

Regards,

0 Kudos

4,486 Views
jmariathas
Contributor I

Hello gusarambula,

Thanks for the response,

When I add in DEPEDNS += “gbm”

I get the error Nothing provides gbm.

When I add in DEPENDS += “libgbm”

I in on the following error.

NOTE: Executing SetScene Tasks

ERROR: libgbm-10.0.0-r0 do_packagedata_setscene: The recipe libgbm is trying to install files into a shared area when those files already exist. Those files and their manifest location are:

/mnt/hd/yocto-2.5/build/tmp/pkgdata/cgtimx6/runtime/libgbm-dev

(matched in manifest-cgtimx6-mesa.packagedata)

/mnt/hd/yocto-2.5/build/tmp/pkgdata/cgtimx6/runtime/libgbm

(matched in manifest-cgtimx6-mesa.packagedata

manifest-cgtimx6-imx-gpu-viv.packagedata)

Please verify which recipe should provide the above files.

The build has stopped, as continuing in this scenario WILL break things - if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would, however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error, however switching DISTRO_FEATURES on an existing build directory is not supported - you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_DUPWHITELIST may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above.

ERROR: libgbm-10.0.0-r0 do_packagedata_setscene: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases.

WARNING: Logfile for failed setscene task is /mnt/hd/yocto-2.5/build/tmp/work/armv7at2hf-neon-mx6qdl-fslc-linux-gnueabi/libgbm/10.0.0-r0/temp/log.do_packagedata_setscene.4326

WARNING: Setscene task (/mnt/hd/yocto-2.5/sources/meta-ti/recipes-graphics/gbm/libgbm_10.0.0.bb:do_packagedata_setscene) failed with exit code '1' - real task will be run instead

NOTE: Executing RunQueue Tasks

ERROR: libgbm-10.0.0-r0 do_packagedata: The recipe libgbm is trying to install files into a shared area when those files already exist. Those files and their manifest location are:

/mnt/hd/yocto-2.5/build/tmp/pkgdata/cgtimx6/runtime/libgbm-dev

(matched in manifest-cgtimx6-mesa.packagedata)

/mnt/hd/yocto-2.5/build/tmp/pkgdata/cgtimx6/runtime/libgbm

(matched in manifest-cgtimx6-mesa.packagedata

manifest-cgtimx6-imx-gpu-viv.packagedata)

Please verify which recipe should provide the above files.

The build has stopped, as continuing in this scenario WILL break things - if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would, however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error, however switching DISTRO_FEATURES on an existing build directory is not supported - you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_DUPWHITELIST may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above.

ERROR: libgbm-10.0.0-r0 do_packagedata: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases.

ERROR: libgbm-10.0.0-r0 do_packagedata: Function failed: sstate_task_postfunc

ERROR: Logfile of failure stored in: /mnt/hd/yocto-2.5/build/tmp/work/armv7at2hf-neon-mx6qdl-fslc-linux-gnueabi/libgbm/10.0.0-r0/temp/log.do_packagedata.4339

ERROR: Task (/mnt/hd/yocto-2.5/sources/meta-ti/recipes-graphics/gbm/libgbm_10.0.0.bb:do_packagedata) failed with exit code '1'

0 Kudos