Packages using provided dependencies may not be emergable if the build script involves using pkg-config. For example, on my system, I installed Imlib2 manually in /usr/local, and then tried emerging enlightemnent 16.8. enlightenment could not build because pkg-config did not see imlib2.pc, installed as /usr/local/lib/pkgconfig/imlib2.pc. One possible solution is to add /usr/local/lib/pkgconfig to the search path: In /etc/env.d/00basic, add the line: PKG_CONFIG_PATH="/usr/local/lib/pkgconfig" /etc/env.d/00basic looks like the best place to me, because that is also where LDPATH="/usr/local/lib" is located. A patch is attached
Created attachment 84754 [details, diff] patch for /etc/env.d/00basic Patch referenced in above comment
*** Bug 130864 has been marked as a duplicate of this bug. ***
In my system PKG_CONFIG_PATH is set to /usr/qt/3/lib/pkgconfig , because there is no other setting in /etc/env.d/. So I guess there should also be a reference to /usr/lib/pkgconfig.
Created attachment 100654 [details, diff] Patch to the current 00basic file Here goes a patch against my current 00basic file, with the change above.
We have decided not to apply the patch. By default, having portage use non-portage installed packages is not a good idea. Any reported problems would be harder to diagnose and fix if /usr/local/lib/pkgconfig was included. A better way to go about this would be creating ebuilds for the packages you need and using portage to install them. You can find us on #gentoo-desktop on freenode if you would like to discuss this further. Thanks!
