[Solved] Upgrade then Downgrade glib; Now Compile Errors

[jasn]

Hi All,

I have two Gentoo installs here. On one I had upgraded to glib-2.15.4 from the desktop-effects overlay, and that was creating a problem for me with regards to re-compiling gnome-vfs-2.20.1-r1. Downgrading to glib-2.14.6 solved that problem, but created a new one. I need to rebuild something on my system that was affected by the upgrade and then downgrade of glib. Another forum user pointed out to me the necessity of rebuilding dbus-glib to solve unresolved symbols in /usr/lib/libdbus-glib-1.so, which I did, and that fixed one problem caused by this upgrade/downgrade. However, the problem I have now is with an undefined reference to `g_assertion_message', that is cropping up on several unrelated compiles. Here are the relevant sections from emerging several packages which are affected;

gnome-vfs-2.20.1-r1

[Wormo]

Have you tried running revdep-rebuild to recompile anything affected by your library changes?

[jasn]

[Wormo]

Did you try passing '--library /usr/lib/libglib.*' to revdep-rebuild, since you know that the breakage is related to glib?

[jasn]

That's a good suggestion that I hadn't tried. However trying it now didn't indicate anything wrong.

[jasn]

I'm an idiot.. (again unfortunately..)

On a lark and looking at the libraries mentioned above that contain the undefined references, I decided to try the following;

1) re-emerge the owning package of libavahi-glib.so, which is avahi. Now gnome-vfs emerges and compiles clean.
2) re-emerge the owning package of libgconfmm-2.6.so, which is gconfmm. Now libgnomeuimm emerges and compiles clean.
3) re-emerge the owning package of libwx_gtk2u_adv-2.8.so, which is wxGTK. Now truecrypt emerges and compiles clean.

It wasn't the upgraded glib, but a matter of finding the packages that I must have built against the upgraded glib. Nice that Gentoo was trying to tell me exactly which ones, and embarrassing that I was thinking it was much more complicated than that. My only hope is that I didn't have too big of an audience watching me fumble around on this one.. (now where did I put that fig leaf..?)

[Wormo]

Did you notice that revdep-rebuild was looking for packages built against libglib.a, but not libglib.so?? If it had worked the way I'd expect it to, then it would have found things like avahi and wxGTK that had been built against the other glib. Either there is something wrong with the way I told you to call it or it's a revdep-rebuild bug.

Either way there's no need for you to be embarrassed, ideally calling revdep-rebuild without args like you did in the first place would have handled the problem (getting revdep-rebuild to be smart enough to work the way we would like is of course easier said than done).

[OldJoe]

Hey folks,

I have a similar problem. I'm currently installing (literally) gentoo on my new notebook and since I have a 64bit CPU I use the amd64 version. While installing Gnome errors like yours

[dunkirk]

In my case, I had allowed my (old) stable system to emerge an unstable version of glib to support vinagre (a Gnome-based VNC viewer). This had allowed several packages to get installed that depended on it until it hit one that actually threw an error with the new layout. Based on what I read here, I did the following:

for i in `equery d glib|awk '{print $1}'`; do emerge -1 =$i; done

I was hitting this problem on a new install (I've been bringing over my old list of packages in /var/lib/portage/world and the exceptions in /etc/portage/*), so the packages I had to re-emerge was fairly small, but it cleared the problem, and Gnome is now emerging.
_________________
Acts 17:28, "For in Him we live, and move, and have our being."