I'm not sure if this has happened because of discrepancies between the required (by Mono) and asked-for (by emerge) glibcs, but here goes: <snip> checking size of void *... 4 checking for pkg-config... /usr/bin/pkg-config 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 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 checking for glib-2.0 >= 1.3.11... 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 configure: error: Library requirements (glib-2.0 >= 1.3.11) not met; consider adjusting the PKG_CONFIG_PATH environment variable if your libraries are in a nonstandard prefix so pkg-config can find them. !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 4, Exitcode 1 !!! ./configure failed !!! emerge aborting on /usr/portage/dev-lang/mono/mono-0.13.ebuild . bash-2.05a# find / -name glib-2.0.pc doesn't turn up anything, nor does \*glib-2.0.pc\*.
emerge --clean rsync && emerge -u glib you should be good then... we'll fix this. thx
Added >=glib-2.x to deps. Never showed up in QA tests as all the testers had glib-2.x installed. Bug submitter has 1.3.11 installed. Commited ebuild change to cvs. Should hit mirrors within the hour. you will need to emerge --clean rsync to pickup changed ebuild. This will also allow you to run 'emerge -up world' showing a list of the out of date packages installed. 'emerge -u world' to upgrade them.
