Created attachment 352624 [details] partial (relevant) part of output from revdep-rebuild -dp Yes, I have cleared /var/cache/revdep-rebuild/ After the binutils update: # ldd /usr/lib/cairo/libcairo-trace.so.0.0.0 linux-vdso.so.1 (0x00007fff531b3000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fa3b0704000) libz.so.1 => /lib64/libz.so.1 (0x00007fa3b04ee000) libdl.so.2 => /lib64/libdl.so.2 (0x00007fa3b02e9000) libbfd-2.22.so => not found libc.so.6 => /lib64/libc.so.6 (0x00007fa3aff41000) libgcc_s.so.1 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so.1 (0x00007fa3afd2a000) /lib64/ld-linux-x86-64.so.2 (0x00007fa3b0b7b000) # ls -al /usr/x86_64-pc-linux-gnu/lib/ total 20 drwxr-xr-x 2 root root 4096 2013-07-03 21:37:57 ./ drwxr-xr-x 7 root root 4096 2013-06-16 09:43:55 ../ lrwxrwxrwx 1 root root 56 2013-07-03 21:37:57 ldscripts -> /usr/lib64/binutils/x86_64-pc-linux-gnu/2.23.1/ldscripts/ lrwxrwxrwx 1 root root 63 2013-07-03 21:37:57 libbfd-2.23.1.so -> /usr/lib64/binutils/x86_64-pc-linux-gnu/2.23.1/libbfd-2.23.1.so* lrwxrwxrwx 1 root root 56 2013-07-03 21:37:57 libbfd.so -> /usr/lib64/binutils/x86_64-pc-linux-gnu/2.23.1/libbfd.so* lrwxrwxrwx 1 root root 58 2013-07-03 21:37:57 libiberty.a -> /usr/lib64/binutils/x86_64-pc-linux-gnu/2.23.1/libiberty.a lrwxrwxrwx 1 root root 67 2013-07-03 21:37:57 libopcodes-2.23.1.so -> /usr/lib64/binutils/x86_64-pc-linux-gnu/2.23.1/libopcodes-2.23.1.so* lrwxrwxrwx 1 root root 60 2013-07-03 21:37:57 libopcodes.so -> /usr/lib64/binutils/x86_64-pc-linux-gnu/2.23.1/libopcodes.so* # ls -al /usr/lib64/binutils/x86_64-pc-linux-gnu/2.23.1/ total 2496 drwxr-xr-x 4 root root 4096 2013-07-03 21:37:53 ./ drwxr-xr-x 3 root root 4096 2013-07-03 21:37:57 ../ drwxr-xr-x 2 root root 4096 2013-07-03 21:37:53 include/ drwxr-xr-x 2 root root 4096 2013-07-03 21:37:53 ldscripts/ -rwxr-xr-x 1 root root 1099688 2013-07-03 21:37:33 libbfd-2.23.1.so* lrwxrwxrwx 1 root root 16 2013-07-03 21:37:53 libbfd.so -> libbfd-2.23.1.so* -rw-r--r-- 1 root root 458000 2013-07-03 21:37:34 libiberty.a -rwxr-xr-x 1 root root 978928 2013-07-03 21:37:34 libopcodes-2.23.1.so* lrwxrwxrwx 1 root root 20 2013-07-03 21:37:53 libopcodes.so -> libopcodes-2.23.1.so* # revdep-rebuild -p * Configuring search environment for revdep-rebuild * Checking reverse dependencies * Packages containing binaries and libraries broken by a package update * will be emerged. * Collecting system binaries and libraries * Generated new 1_files.rr * Collecting complete LD_LIBRARY_PATH * Generated new 2_ldpath.rr * Checking dynamic linking consistency [ 100% ] * Dynamic linking on your system is consistent... All done. Ran in debug mode (saving output), and eventually found (in attachment): There is at least one other package (searching for " not found") being missed.
What version of gentoolkit is this. Also is the breakage still existing on your system? There is a python version of revdep-rebuild installed with recent gentoolkit versions. can you run revdep-rebuild.py on your system to ensure it is not missing your breakage?
> What version of gentoolkit is this. app-portage/gentoolkit-0.3.0.7 > Also is the breakage still existing on your system? The problem has disappeared, and I now have a vague idea of what caused it (but not why it happened). Here is part of the output for the other (formerly) broken package: + : + for target_file in '"${files[@]}"' + [[ /usr/lib64/binutils/armv6j-hardfloat-linux-gnueabi/2.22/libopcodes-2.22.so != *.la ]] ldd "$target_file" 2>> "$ERRORS_FILE" | sort -u) ldd "$target_file" 2>> "$ERRORS_FILE" | sort -u ++ ldd /usr/lib64/binutils/armv6j-hardfloat-linux-gnueabi/2.22/libopcodes-2.22.so ++ sort -u + ldd_output=' /lib64/ld-linux-x86-64.so.2 (0x00007f31258b7000) libbfd-2.22.so => not found libc.so.6 => /lib64/libc.so.6 (0x00007f31252c9000) linux-vdso.so.1 (0x00007fff45fff000)' + ldd_status=0 So sys-devel/binutils-2.23.1 became stable and was installed on 0703. Then revdep-rebuild started missing these packages. Then cross-armv6j-hardfloat-linux-gnueabi/binutils-2.23.1 just became stable and was installed a few hours ago. After that, revdep-rebuild found the breakage with libcairo-trace, and corrected it. So this apparently had something to do with the crossdev packages (which I do not understand AT ALL). I hope that this is enough information to track this bug down, because it seems like one that could bite people much worse at some point in the future.