While trying to sort out why some package did not install properly I found this weird behavior of pkgconf:
When I ask pkgconf to see if a package proj exists (which I know it does!), it says nothing:
# pkgconf --exists proj
but if I ask for the path to its pc file it gives the correct answer:
pkgconf --path proj
/usr/local/lib64/pkgconfig/proj.pc
What is going on here?
Also when starting to study this problem, I saw that the variable PKG_CONFIG_PATH was empty. I added the paths later.
Is this the expected behavior of pkgconf ?
Is anyone familiar with this in openSUSE?
I am using v. 1.8.0-1.6 from the main repo.
# zypper if pkgconf
Loading repository data...
Reading installed packages...
Information for package pkgconf:
--------------------------------
Repository : Main Repository (OSS)
Name : pkgconf
Version : 1.8.0-1.6
Arch : x86_64
Vendor : openSUSE
Installed Size : 78.3 KiB
Installed : Yes (automatically)
Status : up-to-date
Source package : pkgconf-1.8.0-1.6.src
Upstream URL : http://pkgconf.org/
Summary : Package compiler and linker metadata toolkit
Description :
pkgconf is a program which helps to configure compiler and linker flags
for development frameworks. It is similar to pkg-config from freedesktop.org
and handles .pc files in a similar manner as pkg-config.