Summary: | gnome-base/gnome-panel-2.26.3 failes to compile in @preserved-rebuild after libxcb update to 1.4 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Steffen Hau <steffen> |
Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | rdwald |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 263083 |
Description
Steffen Hau
2009-08-20 11:42:20 UTC
That sounds like a libtool error. I'd bet a buck that it was generated with libtool 1.5 I am having the same problem after updating libxcb to 1.4, I have the latest libtool installed and get the same error. I am still in the process of rebuilding my system after the mess that the libxcb and jpeg updates left. I will see if after repairing everything else if the same error occurs. On my system, thos occured as long as /usr/lib/libpanel-applet.so* existed. Removing it solved this issue for me. But of course, there must be another way. Are you talking about emerging it after the libxcb-1.4 upgrade? I tried moving those files to trash and then emerging only to get the same error. (In reply to comment #4) > Are you talking about emerging it after the libxcb-1.4 upgrade? I tried moving > those files to trash and then emerging only to get the same error. emerge -C gnome-panel && emerge -1 gnome-panel Fixed it. emerge -1 gnome-desktop && emerge --unmerge gnome-panel && emerge -1 gnome-panel so that means gnome-panel is linking against with its old installation maybe. That's why I was betting the tarball was generated with libtool 1.5 and not 2.2 where lots of such bugs have been fixed. (same bug we had with e-d-s a while ago) Cheers Not directly related to this bug, but I had a similar problem with a different package (app-i18n/uim-1.5.6-r1) linking against its already-installed version, causing problems with the libxcb-1.4 update (Bug #284815). I figured I'd cross-link these bugs in the event that there's some common cause. Like I said in comment #8, libtool 1.5 is usually the culprit. Especially when you have a library that deps on another library. That use case is very common in big gnome apps (e-d-s, evolution, anjuta, ...). I'm not sure what uim uses, but it does look like libtool so that'd be a first start. The problem is that the libtool you have on your system isn't used at all. The broken libtool scripts are the ones shipped inside the tarball, so you have to convince upstream to stop building their tarballs with a broken and dead libtool. Thanks Same problem after upgrade from 1.5x to 2.2.6a. Following workarround works for me. echo "sys-devel/libtool **" >> /etc/portage/packages.keywords/sys-devel emerge libtool (libtool-9999) revdep-rebuild --library libxcb-xlib.so.0.0.0 This build the cvs-version of libtool (also 2.2.6). After this run revdep-rebuild to fix broken packages. This is not the best way, i know. Please read this ... http://www.gentoo.org/proj/en/desktop/x/x11/libxcb-1.4-upgrade-guide.xml ... the correct way to fix the problem. (In reply to comment #12) > Please read this ... > > http://www.gentoo.org/proj/en/desktop/x/x11/libxcb-1.4-upgrade-guide.xml > > ... the correct way to fix the problem. > @reporter: please follow the guide to fix the problem (if you haven't already) |