[vbox-dev] Package glib-2.0 was not found in the pkg-config search path
John Lumby
jlumby at bluecatnetworks.com
Wed Oct 26 14:31:45 UTC 2022
Building 6.1.38 on a linux system running kernel 5.9.16 and glibc-2.35,
and with glib-2.0 2.58.3 installed and working,
and with
PKG_CONFIG_PATH=/opt/openssl/lib/pkgconfig:/usr/local/xorg-git-current/xorg-build/lib/pkgconfig:/usr/local/xorg-git-current/xorg-build/share/pkgconfig:/usr/local/lib/pkgconfig:/usr/lib/x86_64-linux-gnu/pkgconfig:/usr/share/pkgconfig:/usr/lib/pkgconfig
and glib-2.0 pkg conf file here
-rw-r--r-- 1 root root 425 Nov 6 2019 /usr/lib/x86_64-linux-gnu/pkgconfig/glib-2.0.pc
and pkg-config reporting
pkg-config --modversion glib-2.0
2.58.3
the kmk command spits this out :
build debug: VBOX_WITH_NO_GCC_WARNING_POLICY is enabled
Package glib-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `glib-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'glib-2.0' found
Any idea why it is doing this? I could not find where in the build jungle it is checking this. But I do note that the config.log from configure does not mention glib at all. Why is kmk doing this instead of configure? All very strange.
I eventually figured out a very horrible way of forcing the build to go through using the CFLAGS and LIBS from the /usr/lib/x86_64-linux-gnu/pkgconfig/glib-2.0.pc, i.e. using the run-time glib-2.0 2.58.3 , and -- it works just fine. So the problem is not with the installed glib-2.0.
Cheers, John Lumby
More information about the vbox-dev
mailing list