I was attempting to emerge kde and I get an error when attempting to compile imlib. It reports that it can't find libglib.la in the /var/tmp/portage directory. Doing a grep in /usr/lib showed that several files incorrectly reported that glib was located in the /var/tmp/portage directory. The version of glib used was glib-1.2.10-r5. Reproducible: Always Steps to Reproduce: 1. 2. 3. A temporary workaround is to grep /usr/lib for the incorrect entries and manually change them to /usr/lib/libglib.la
herds: I've seen this problem quite often and I guess it's not only imagemagick overwriting libtool (or invalid ebuilds). Usually `find /usr/lib -iname "*\.la" -exec sed -i -r -e "s:/var/tmp/portage/.*/image/::g" '{}' \;` is a workaround for the problem, but the changed mtime will cause portage not to uninstall the affected file(s) afaik. Either there's a bug in some .la rewrite code which needs to get fixed or/and it should never be possible, to overwrite libtool files by other ebuilds, even w/o having the collision-protect feature enabled.
you neglected to provide `emerge info` like the bug report page says to also, if you `emerge =glib-1*`, does the .la file still contain /var/tmp/portage references ?
Created attachment 44579 [details] output of emerge info
doing an emerge =glib-1* has the correct paths in libglib.la. The files that were affected and had the wrong path to libglib.la were libgtk.la and libgdk.la. The problem arose when I started emerging a new system in this order: emerge system emerge xorg-x11 emerge kde
