Can someone familiar with the ebuild mechanisms look this over and figure out how the opensp dynamic library needed by openjade disappeared without triggering a recompile of openjade? I think gnome-vfs is just "he who smelt it" in this tragedy. While updating my world gnome-vfs failed to compile: touch sgml-build.stamp touch ./sgml.stamp *** Building HTML *** test -d ./html || (rm -rf ./html && mkdir ./html) cd ./html && gtkdoc-mkhtml gnome-vfs ../gnome-vfs-docs.sgml /usr/bin/openjade: error while loading shared libraries: libosp.so.3: cannot open shared object file: No such file or directory make[2]: *** [html-build.stamp] Error 127 make[2]: Leaving directory `/var/tmp/portage/gnome-vfs-1.0.5-r4/work/gnome-vfs-1.0.5/doc' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/gnome-vfs-1.0.5-r4/work/gnome-vfs-1.0.5' make: *** [all-recursive-am] Error 2 !!! ERROR: gnome-base/gnome-vfs-1.0.5-r4 failed. !!! Function src_compile, Line 74, Exitcode 2 !!! (no error message) !!! If you need support, post the topmost build error, NOT this status message. Poking around in the bug database, the lightbulb finally came on over my head: nile:519 # ldd /usr/bin/openjade | grep libosp libospgrove.so.0 => /usr/lib/libospgrove.so.0 (0x40208000) libosp.so.3 => not found Somehow libosp got upgraded, and openjade wasn't recompiled. It may have something to do with these lines logged in /var/log/emerge.log: 1111078634: Started emerge on: Mar 17, 2005 11:57:14 1111078634: *** emerge --update --verbose --deep world 1111078645: >>> emerge (1 of 17) app-text/opensp-1.5.1 to / 1111078645: === (1 of 17) Cleaning (app-text/opensp-1.5.1::/usr/portage/app-tex t/opensp/opensp-1.5.1.ebuild) 1111078646: === (1 of 17) Compiling/Merging (app-text/opensp-1.5.1::/usr/portag e/app-text/opensp/opensp-1.5.1.ebuild) 1111079128: === (1 of 17) Post-Build Cleaning (app-text/opensp-1.5.1::/usr/port age/app-text/opensp/opensp-1.5.1.ebuild) 1111079131: >>> AUTOCLEAN: app-text/opensp 1111079137: === Unmerging... (app-text/opensp-1.5-r1) 1111079149: >>> unmerge success: app-text/opensp-1.5-r1 1111079150: ::: completed emerge (1 of 17) app-text/opensp-1.5.1 to / 1111079150: >>> emerge (2 of 17) app-text/docbook-xsl-stylesheets-1.66.1 to / 1111079150: === (2 of 17) Cleaning (app-text/docbook-xsl-stylesheets-1.66.1::/u sr/portage/app-text/docbook-xsl-stylesheets/docbook-xsl-stylesheets-1.66.1.ebuil d) 1111079151: === (2 of 17) Compiling/Merging (app-text/docbook-xsl-stylesheets-1 .66.1::/usr/portage/app-text/docbook-xsl-stylesheets/docbook-xsl-stylesheets-1.6 6.1.ebuild) I'm assuming I should re-emerge the openjade package which hopefully will result in it being linked against my existing libosp . I hope this bug report is useful to the next person who gets this error. Reproducible: Always Steps to Reproduce: I'm not sure what steps could be taken to put the system into this malfunctioning state. Expected Results: The libosp dynamic library should not have been removed without a recompilation of the packages which depend on it. Portage 2.0.51.19 (default-linux/x86/2005.0/2.4, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.4.28-gentoo-r8 i686) ================================================================= System uname: 2.4.28-gentoo-r8 i686 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 23 2005, 16:44:54)] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.4.22-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=i686 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=i686 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/home/thoth/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow 3dnowex X Xaw3d acl alsa apache2 apm arts avi bash-completion berkdb bitmap-fonts bonobo bzlib cdr crypt cups curl divx4linux doc dv dvd dvdr dvdread edl emboss encode esd fam ffmpeg foomaticdb gdbm gif gnome gpm gtk gtk2 gtkhtml guile imagemagick imlib ipv6 java jpeg junit kde libg++ libwww mad maildir mikmod mjpegi mmx mng motif mp3 mpeg mysql mythtv ncurses nls nojython ogg oggvorbis opengl oss pam pcmcia pdflib perl png python qt quicktime readline sdl spell sse sse2 ssl svg svga tcltk tcpd theora tiff transcode truetype truetype-fonts type1-fonts unicode v4l vim-with-x vorbis win32codecs wmf xinerama xml xml2 xmms xv xvid yv12 zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
doing an emerge -1 openjade did allow the update of gnome-vfs to complete. Other users who encounter this problem can use that workaround. The only remaining issue for the gentoo maintainers is "how did openjade get the libosp rug pulled out from under it?"
I have since learned of the revdep-rebuild tool (which is part of the gentoolkit ebuild which is not installed by default, but appears to be required to maintain a working gentoo system). *** This bug has been marked as a duplicate of 1991 ***