Summary: | dev-util/anjuta-2.24.2 has a avahi memory effect | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sven Müller <musv> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | pacho |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 238650 |
Description
Sven Müller
2009-04-08 10:56:15 UTC
What you are facing is a problem very similar (in a way) to bug 158476. See if for a solution. Ok, I solved the problem. The solucion is to deinstall Anjuta completely and reinstall it. Only to update the package doesn't touch the files in /usr/lib/anjuta. Therefore it seems to be necessary to deinstall Anjuta first. Only that removes the /usr/lib/anjuta-directory. What to do now? (In reply to comment #2) > What to do now? I'd say we wait for input from the anjuta maintainer (In reply to comment #2) > Ok, I solved the problem. The solucion is to deinstall Anjuta completely and > reinstall it. > > Only to update the package doesn't touch the files in /usr/lib/anjuta. > Therefore it seems to be necessary to deinstall Anjuta first. Only that removes > the /usr/lib/anjuta-directory. this sounds wrong, I don't see why reinstalling anjuta wouldn't erase existing files unless anjuta somehow relinks against installed anjuta libs all the way. It wouldn't be the first time though. anjuta 2.24.x was still generated with libtool 1.5 last time I checked and since it was one of the biggest users of "libs linking against other libs within the same project", I would definitely bet a buck that libtool is to blame. Maybe 2.26 is generated with libtool 2.2? In any case, it'd be worth checking. avahi is picked up somehow by the build system and creeps in every libs installed by anjuta while there is no reason for it being the case. We really need to review their autofoo since we concluded with remi that it was doing way too many suspicious stuff already. (In reply to comment #5) > anjuta 2.24.x was still generated with libtool 1.5 last time I checked and > since it was one of the biggest users of "libs linking against other libs > within the same project", I would definitely bet a buck that libtool is to > blame. > > Maybe 2.26 is generated with libtool 2.2? In any case, it'd be worth checking. > Still valid with anjuta-2.26* ? or even better with anjuta-2.28 ;-) Please get back to us. Thanks |