This is on a system just installed today. I noticed one or two other bugs claiming that portage has removed installation of the pkg_config binary. I can also see that pkg_config is installed on older systems, but none of the boxes installed within the last week. gentoolkit/etc is installed. Reproducible: Always Steps to Reproduce: 1.setup a new box from scratch using latest ebuilds/etc 2.emerge nagios or anything else that requires manual ebuild config run after install 3. notice warning about being unable to execute pkg_config Actual Results: monitor nagios-core-1.2 # !213 ebuild /var/db/pkg/net-analyzer/nagios-core-1.2/nagios-core-1.2.ebuild config /usr/lib/portage/bin/ebuild.sh: line 1448: pkg_config: command not found Expected Results: completed install USE="apache2 async catalyst cgi curl devfs26 doc evms2 foreign-package mmx \ nagios-dns nagios-ntp nagios-ping nagios-ssh nptl openssh pcap \ pg-intdatetime pg-vacuumdelay postgres snmp sse -oss -apm -arts -avi \ -crypt -cups -encode -foomaticdb -gpm -gtk -gtk2 -kde -gnome -mad \ -mikmod -motif -mpeg -opengl -qt -quicktime -sdl -tcpd -truetype -X \ -xmms -xv"
Do you have pkg_config on your system?
no, pkg_config was not installed during the emerge process for portgage or gentoolkit. monitor root # find / -name "pkg_config" -print monitor root #
Not a portage bug... Some package is requiring the using pkg_config and should have the dep in it.
I think you must change the Summary of this bug. This is not a bug for net-analyzer/nagios-core its for portage, and maybe change also the Product for Portage Development (?). Same problem here. portage 2.0.50-r7 installed here but the error is little different: "/usr/sbin/ebuild.sh: line 1334: pkg_config: command not found" (the line number, which version of portage do you have installed?)
This is totally a portage bug carpaski. ebuild.sh should supply a default pkg_config function so if the ebuild doesn't supply one of its own, ebuild ... config still works. This doesn't have anything to do with a depend on pkgconfig.
i think the 'pkg_config' and 'pkg-config' scripts are getting confused :)
Ok. So the bug was that the ebuild didn't have a pkg_config function in it. Calling config on the ebuild fails because IT CANNOT do it... Why should portage ignore the fact that the ebuild cannot do what was requested? I can add an eerror message and exit with an error if you'd like, but this is a reasonable and duely CAUSED failure.
ebuild /var/db/pkg/net-analyzer/nagios-core-1.2/nagios-core-1.2.ebuild config /usr/lib/portage/bin/ebuild.sh: line 1448: pkg_config: command not found that is a horrible message ... who the hell is supposed to know what that means ? the thing we're trying to get at is this: please add something like this to ebuild.sh: pkg_config() { eerror "This ebuild does not have a config function." }
I've just included the error message in CVS.
in .51_pre18 (probably released earlier).
