After upgrading my amd64 system from dev-libs/expat-1.95.8 to dev-libs/expat-2.0.1, /usr/lib64/libexpat.so.0 was removed from my system. revdep-rebuild tells me I need to rebuild a large number of packages. One is x11-libs/gtk+. Rebuilding gtk+2.10.13 upgrading to (masked on amd64) gtk+2.10.14 fails to build and install complaining that /usr/lib64.libexpat.so.0 is required. Reproducible: Always Steps to Reproduce: emerge --sync emerge --oneshot expat emerge --oneshot gtk+ * error * Actual Results: x86_64-pc-linux-gnu-gcc -shared .libs/imti-et.o -Wl,--rpath -Wl,/var/tmp/portage/x11-libs/gtk+-2.10.14/work/gtk+-2.10.14/gdk-pixbuf/.libs -Wl,--rpath -Wl,/var/tmp/portage/x11-libs/gtk+-2.10.14/work/gtk+-2.10.14/gdk/.libs -Wl,--rpath -Wl,/var/tmp/portage/x11-libs/gtk+-2.10.14/work/gtk+-2.10.14/gtk/.libs -L/var/tmp/portage/x11-libs/gtk+-2.10.14/work/gtk+-2.10.14/gdk-pixbuf/.libs -L/var/tmp/portage/x11-libs/gtk+-2.10.14/work/gtk+-2.10.14/gdk/.libs ../../gdk-pixbuf/.libs/libgdk_pixbuf-2.0.so -L/usr/lib64 ../../gdk/.libs/libgdk-x11-2.0.so ../../gtk/.libs/libgtk-x11-2.0.so /usr/lib64/libpangocairo-1.0.so /usr/lib64/libpango-1.0.so /usr/lib64/libX11.so /usr/lib64/libXfixes.so /usr/lib64/libatk-1.0.so /usr/lib64/libgobject-2.0.so /usr/lib64/libgmodule-2.0.so -ldl /usr/lib64/libglib-2.0.so /usr/lib64/libcairo.so -lm -march=athlon64 -Wl,-soname -Wl,im-ti-et.so -o .libs/im-ti-et.so creating im-ti-et.la (cd .libs && rm -f im-thai.la && ln -s ../im-thai.la im-thai.la) /bin/sh ../../libtool --mode=link x86_64-pc-linux-gnu-gcc -DG_DISABLE_DEPRECATED -march=athlon64 -O2 -pipe -Wall -o im-viqr.la -rpath /usr/lib64/gtk-2.0/2.10.0/immodules -rpath /usr/lib64/gtk-2.0/2.10.0/immodules -avoid-version -module imviqr.lo ../../gdk-pixbuf/libgdk_pixbuf-2.0.la ../../gdk/libgdk-x11-2.0.la ../../gtk/libgtk-x11-2.0.la -lpangocairo-1.0 -lpango-1.0 -lX11 -lXfixes -latk-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 -lcairo -lm (cd .libs && rm -f im-ti-er.la && ln -s ../im-ti-er.la im-ti-er.la) (cd .libs && rm -f im-ti-et.la && ln -s ../im-ti-et.la im-ti-et.la) x86_64-pc-linux-gnu-gcc -shared .libs/imviqr.o -Wl,--rpath -Wl,/var/tmp/portage/x11-libs/gtk+-2.10.14/work/gtk+-2.10.14/gdk-pixbuf/.libs -Wl,--rpath -Wl,/var/tmp/portage/x11-libs/gtk+-2.10.14/work/gtk+-2.10.14/gdk/.libs -Wl,--rpath -Wl,/var/tmp/portage/x11-libs/gtk+-2.10.14/work/gtk+-2.10.14/gtk/.libs -L/var/tmp/portage/x11-libs/gtk+-2.10.14/work/gtk+-2.10.14/gdk-pixbuf/.libs -L/var/tmp/portage/x11-libs/gtk+-2.10.14/work/gtk+-2.10.14/gdk/.libs ../../gdk-pixbuf/.libs/libgdk_pixbuf-2.0.so -L/usr/lib64 ../../gdk/.libs/libgdk-x11-2.0.so ../../gtk/.libs/libgtk-x11-2.0.so /usr/lib64/libpangocairo-1.0.so /usr/lib64/libpango-1.0.so /usr/lib64/libX11.so /usr/lib64/libXfixes.so /usr/lib64/libatk-1.0.so /usr/lib64/libgobject-2.0.so /usr/lib64/libgmodule-2.0.so -ldl /usr/lib64/libglib-2.0.so /usr/lib64/libcairo.so -lm -march=athlon64 -Wl,-soname -Wl,im-viqr.so -o .libs/im-viqr.so creating im-viqr.la (cd .libs && rm -f im-viqr.la && ln -s ../im-viqr.la im-viqr.la) ../../gtk/gtk-query-immodules-2.0 im-xim.la im-am-et.la im-cedilla.la im-cyrillic-translit.la im-inuktitut.la im-ipa.la im-thai.la im-ti-er.la im-ti-et.la im-viqr.la > gtk.immodules /var/tmp/portage/x11-libs/gtk+-2.10.14/work/gtk+-2.10.14/gtk/.libs/lt-gtk-query-immodules-2.0: error while loading shared libraries: libexpat.so.0: cannot open shared object file: No such file or directory make[3]: *** [gtk.immodules] Error 127 make[3]: Leaving directory `/var/tmp/portage/x11-libs/gtk+-2.10.14/work/gtk+-2.10.14/modules/input' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/x11-libs/gtk+-2.10.14/work/gtk+-2.10.14/modules' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/x11-libs/gtk+-2.10.14/work/gtk+-2.10.14' make: *** [all] Error 2 !!! ERROR: x11-libs/gtk+-2.10.14 failed. Call stack: ebuild.sh, line 1632: Called dyn_compile ebuild.sh, line 983: Called qa_call 'src_compile' ebuild.sh, line 44: Called src_compile gtk+-2.10.14.ebuild, line 108: Called die !!! compile failed !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/tmp/portage/x11-libs/gtk+-2.10.14/temp/build.log'. Expected Results: Successful build
*** This bug has been marked as a duplicate of bug 128069 ***
bug 128069 indicates that the problem can be solved by revdep-rebuild. revdep-rebuild does NOT solve my problem, so it is NOT a duplicate of that bug. I have ran: emerge --sync rm .revdep-rebuild* (to clear rebuild cache) revdep-rebuild --library libexpect.so.0 * error occurs after much verbosity * rm .revdep-rebuild* revdep-rebuild * error occurs again after much verbosity * emerge --update --newuse --deep world rm .revdep-rebuild* revdep-rebuild * error occurs again after much verbosity * The error message is always the same and is already attached to this bug. The list of packages that revdep tries to rebuild every time and always fails on gtk+. Note that the first packages never go away because they are binary and emerging them does not solve the problem. (see bug 175774). The first 3 are: app-emulation/emul-linux-x86-gtklibs-10.0-r1 x11-wm/windowmaker x11-libs/gtk+-2.10.13 I am to much of a newbie to know if these binary libraries are the source of my problem. If I do: equery depends --indirect --depth=3 app-emuluation/emul-linux-x86-xlibs I find that gtk+ indirectly inherits from my binary xlibs as follows: x11-drivers/nvidia-drivers-100.14.09 x11-base/xorg-server-1.2.0-r3 x11-libs/gtk+-2.10.13 (lots of other dependencies removed) If my issue is the binary packages via the nvidia drivers, then all amd64 users using the binary proprietary nvidia drivers should have the same issue. As it stands now, my system will not revdep-rebuild without error and emerge --sync does not help. My system is broken and many applications don't work. (luckly mozilla still runs, but I am afraid to quit it because it may not start again). Please advise what I should do to fix the problem.
So file a bug about revdep-rebuild and attach all the /root/revdep* files there, as well as the revdep-rebuild output. This is not a gtk+ bug. *** This bug has been marked as a duplicate of bug 128069 ***
