Run-time dependency gcr-3 found: NO (tried pkgconfig and cmake) meson.build:195:2: ERROR: Dependency "gcr-3" not found, tried pkgconfig and cmake A full log can be found at /var/tmp/portage/net-libs/libnma-1.8.30/work/libnma-1.8.30-build/meson-logs/meson-log.txt * ERROR: net-libs/libnma-1.8.30::gentoo failed (configure phase): ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_developer-20200813-172142 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-10.2.0 * clang version 10.0.1 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/10/bin /usr/lib/llvm/10 10.0.1 Available Python interpreters, in order of preference: [1] python3.7 [2] python3.9 (fallback) [3] python3.8 (fallback) [4] python3.6 (fallback) [5] python2.7 (fallback) [6] pypy3 (fallback) Available Ruby profiles: [1] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.45.2 * The following VMs are available for generation-2: 1) IcedTea JDK 3.16.0 [icedtea-8] *) IcedTea JDK 3.16.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-8 [2] icedtea-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.8.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Tue Aug 18 01:05:56 AM UTC 2020 emerge -qpvO net-libs/libnma [ebuild N ] net-libs/libnma-1.8.30 USE="introspection pkcs11 -gtk-doc -vala"
Created attachment 655204 [details] emerge-info.txt
Created attachment 655206 [details] emerge-history.txt
Created attachment 655208 [details] environment
Created attachment 655210 [details] etc.portage.tbz2
Created attachment 655212 [details] logs.tbz2
Created attachment 655214 [details] net-libs:libnma-1.8.30:20200818-032442.log
Created attachment 655216 [details] temp.tbz2
Not sure how this could happen after investigating for about 10 minutes. If you can reproduce this, please make sure to attach meson-log.txt. It would show what happened with the check.
appeared recently at the tinderbox image 17.1_desktop-j4-20220119-205952
Created attachment 763653 [details] emerge-info.txt
Created attachment 763654 [details] emerge-history.txt
Created attachment 763655 [details] environment
Created attachment 763656 [details] etc.portage.tar.bz2
Created attachment 763657 [details] logs.tar.bz2
Created attachment 763658 [details] net-libs:libnma-1.8.34:20220126-031438.log
Created attachment 763659 [details] temp.tar.bz2
I have the same problem. meson tries to find gcr-3 via pkg-config with following command: /usr/bin/x86_64-pc-linux-gnu-pkg-config --modversion gcr-3 Wenn executing this command on the shell it returns following: "Package gcr-3 was not found in the pkg-config search path. Perhaps you should add the directory containing `gcr-3.pc' to the PKG_CONFIG_PATH environment variable Package 'gcr-3', required by 'virtual:world', not found" Thus app-crypt/gcr (3.40.0) doesn't install a file called "gcr-3.pc". Instead the package installs a pkg-config file named "gcr-base-3.pc"
(In reply to stephan wezel from comment #17) > I have the same problem. > meson tries to find gcr-3 via pkg-config with following command: > > /usr/bin/x86_64-pc-linux-gnu-pkg-config --modversion gcr-3 > > Wenn executing this command on the shell it returns following: > > "Package gcr-3 was not found in the pkg-config search path. > Perhaps you should add the directory containing `gcr-3.pc' > to the PKG_CONFIG_PATH environment variable > Package 'gcr-3', required by 'virtual:world', not found" > > Thus app-crypt/gcr (3.40.0) doesn't install a file called "gcr-3.pc". > Instead the package installs a pkg-config file named "gcr-base-3.pc" Very interesting. My theory is that there's a race condition in the meson build. Notice that there are two pkgconfig.generate calls whose first argument is gcr_ui_lib. % git grep gcr_ui_lib ui/meson.build:gcr_ui_lib = shared_library(gcr_ui_basename, ui/meson.build:pkgconfig.generate(gcr_ui_lib, ui/meson.build:pkgconfig.generate(gcr_ui_lib, ui/meson.build: link_with: gcr_ui_lib, ui/meson.build: gcr_ui_gir = gnome.generate_gir(gcr_ui_lib, I've confirmed that each is responsible for creating gcr-3.pc and gcr-ui-3.pc: /var/tmp/portage/app-crypt/gcr-3.40.0/image # find -name '*.pc' | sort ./usr/lib64/pkgconfig/gck-1.pc ./usr/lib64/pkgconfig/gcr-3.pc ./usr/lib64/pkgconfig/gcr-base-3.pc /var/tmp/portage/app-crypt/gcr-3.40.0/image # cd `pwd` /var/tmp/portage/app-crypt/gcr-3.40.0/image # find -name '*.pc' | sort ./usr/lib64/pkgconfig/gck-1.pc ./usr/lib64/pkgconfig/gcr-base-3.pc ./usr/lib64/pkgconfig/gcr-ui-3.pc
Rebuild gcr first then build libnma. It worked for me anyways.
I found a solution that worked for me, which was enabling the "gtk" use variable for app-crypt/gcr. The clue came from Stephan Wezel comment showing gcr-3.pc was missing. I created a soft link from /usr/lib64/pkgconfig/gcr-base-3.pc pointing to /usr/lib64/pkgconfig/gcr-3.pc then trying to emerge libnma which then failed on the following: > The Meson build system > Version: 0.60.3 > Source dir: /var/tmp/portage/net-libs/libnma-1.8.34/work/libnma-1.8.34 > Build dir: /var/tmp/portage/net-libs/libnma-1.8.34/work/libnma-1.8.34-build > Build type: native build > Project name: libnma > Project version: 1.8.34 > C compiler for the host machine: x86_64-pc-linux-gnu-gcc (gcc 11.2.1 "x86_64-pc-linux-gnu-gcc (Gentoo Hardened 11.2.1_p20220115 p4) 11.2.1 20220115") > C linker for the host machine: x86_64-pc-linux-gnu-gcc ld.bfd 2.38 > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Checking for type "pid_t" : YES > Message: whether to disable iso-codes at build-time: true > Found pkg-config: /usr/bin/x86_64-pc-linux-gnu-pkg-config (1.8.0) > Run-time dependency iso-codes found: YES 4.9.0 > Message: whether iso-codes has iso_3166 domain: true > Message: whether to enable mobile-broadband-provider-info at build-time: true > Run-time dependency mobile-broadband-provider-info found: YES 20210805 > Run-time dependency gio-2.0 found: YES 2.70.4 > Run-time dependency gmodule-export-2.0 found: YES 2.70.4 > Library m found: YES > Run-time dependency gtk+-3.0 found: YES 3.24.31 > Run-time dependency libnm found: YES 1.32.12 > Run-time dependency gcr-3 found: YES 3.40.0 > Run-time dependency gck-1 found: YES 3.40.0 > > meson.build:255:2: ERROR: Assert failed: gcr support was requested, but the gcr library is not available. Use -Dgcr=false to build without it. > >A full log can be found at /var/tmp/portage/net-libs/libnma-1.8.34/work/libnma-1.8.34-build/meson-logs/meson-log.txt Looking in the log file I found the following: > Compiler stderr: > /var/tmp/portage/net-libs/libnma-1.8.34/work/libnma-1.8.34-build/meson-private/tmp0wbfyg_e/testfile.c:9:14: fatal error: gcr/gcr.h: No such file or directory > 9 | #include <gcr/gcr.h> > | ^~~~~~~~~~~ > compilation terminated. Of the use variables for app-crypt/gcr not enabled, enabling "gtk" made the most sense. Once enabled then reinstalled app-crypt/gcr, both gcr-3.pc and gcr-3.h showed up in the file system. Reinstalling libnma went without event after that.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9b3b2a73afbb5548510b0ee1e8930c3d954a2500 commit 9b3b2a73afbb5548510b0ee1e8930c3d954a2500 Author: Matt Turner <mattst88@gentoo.org> AuthorDate: 2022-10-10 22:21:40 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2022-10-10 22:36:44 +0000 net-libs/libnma: Depend on gcr[gtk] Closes: https://bugs.gentoo.org/737716 Signed-off-by: Matt Turner <mattst88@gentoo.org> dev-libs/glib/glib-2.74.0-r1.ebuild | 2 +- net-libs/libnma/libnma-1.10.2.ebuild | 2 +- net-libs/libnma/libnma-1.8.40-r1.ebuild | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)