Summary: | libglib.la incorrectly points to install directory as being in /var/tmp/portage | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | bhunter1 |
Component: | [OLD] Library | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED NEEDINFO | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | output of emerge info |
Description
bhunter1
2004-11-22 07:39:40 UTC
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 |