Where do I find a package called pkgconfig?

Building firefox gives the following build dependencies:

pkgconfig(alsa) is needed by firefox-102.15.1-1.el9.x86_64
pkgconfig(dri) is needed by firefox-102.15.1-1.el9.x86_64
pkgconfig(gtk+-2.0) is needed by firefox-102.15.1-1.el9.x86_64
pkgconfig(gtk+-3.0) is needed by firefox-102.15.1-1.el9.x86_64
pkgconfig(krb5) is needed by firefox-102.15.1-1.el9.x86_64
pkgconfig(libcurl) is needed by firefox-102.15.1-1.el9.x86_64
pkgconfig(libnotify) >= 0.7.0 is needed by firefox-102.15.1-1.el9.x86_64
pkgconfig(libpulse) is needed by firefox-102.15.1-1.el9.x86_64
pkgconfig(libstartup-notification-1.0) is needed by firefox-102.15.1-1.el9.x86_64
pkgconfig(nspr) >= 4.34 is needed by firefox-102.15.1-1.el9.x86_64
pkgconfig(nss) >= 3.79 is needed by firefox-102.15.1-1.el9.x86_64
pkgconfig(pango) is needed by firefox-102.15.1-1.el9.x86_64
pkgconfig(xrender) is needed by firefox-102.15.1-1.el9.x86_64
pkgconfig(xt) is needed by firefox-102.15.1-1.el9.x86_64
pkgconfig(xtst) is needed by firefox-102.15.1-1.el9.x86_64

but I can find no package called pkgconfig in the Rocky repositories.

Can anybody tell me where I should be looking ?

Many thanks,
Roger.

None of those is actually the ā€œpkgconfigā€. For example,

dnf provides 'pkgconfig(nss)'
dnf rq --whatprovides 'pkgconfig(nss)'

will both tell that feature ā€œpkgconfig(nss)ā€ is provided by package nss-devel.
That feature is info for the build tools on how to include/link the nss library.

Obviously, the build tools do use some utility to read the info and that is the pkgconfig.


One could ask whether there is a file with that name in some package:

dnf provides */pkgconfig

but that output does not make us wiser.

One could ask whether such feature is provided by some packages:

dnf provides pkgconfig
dnf rq --whatprovides pkgconfig

However, one can also ask what the nss-devel does require:

dnf rq --requires nss-devel
dnf rq --requires --resolve nss-devel

Therefore, the installation of nss-devel (or probably any of the needed packages) will auto-install the ā€œpgkconfigā€ too.


Why are you building Firefox? Rocky does provide one?
Are you building with rpmbuild?
The mock supposedly auto-installs those required packages (and does it in ā€œcleanā€ chroot).

Jukka,

Thank you for the superb and rapid reply, full of education - appreciated.

Why are you building Firefox? Rocky does provide one?

There is nothing wrong with the installed prebuilt firefox - I was wanting to look inside it for my own study and education.

Are you building with rpmbuild?

Yes, I was. But now, thanks to you, I can see that mock may be a better way of doing it.

Thanks !
Roger.

Hint:

If you only want to browse code, you neither need to do a full build nor install any dependencies.
This is what I usually do, if I just want to look at the source of some package (As normal user - NOT as root):

dnf download --source firefox
rpm -ivh firefox*.src.rpm
rpmbuild -bp --nodeps ~/rpmbuild/SPECS/firefox*.spec

Browse the code below ~/rpmbuild/BUILD/firefox*/

That practice applies to all builds. (At most the ā€œinstallā€ step may need elevated privileges.)

My remark was referring to the non-build part. Specifically to the invocation of dnf

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.