I have two ~amd64 systems, but strangely, only one has this issue. The problem is that all of the libsmbclient.so dependencies live in /usr/lib/samba and are supposed to be found via the DT_RUNPATH dynamic section attribute in libsmbclient.so. So on the working machine I see: # objdump -p /usr/lib/libsmbclient.so | grep RUNPATH RUNPATH /usr/lib64/samba:/usr/lib64 Whereas on the broken machine I get: # objdump -p /usr/lib/libsmbclient.so | grep RUNPATH RUNPATH /usr/lib64 Which of course yields build failures for anything linking against libsmbclient.so. Both machines differ mainly in their USE flags, so I'll continue to investigate what triggers the problem, but of course something like this should not happen at all, no matter the USE flags.
Okay, this seems to be triggered by FEATURES=distcc. Once I disable distcc, the correct RUNPATH is put into the library. Not sure how to proceed with this. On the one hand, there's a bunch of packages that fail to build with distcc, so maybe we don't care all that much, but those are normally pretty obvious build errors. Whereas in this case, we end up with lots of secondary problems that may be pretty hard to track down for many users.
*** Bug 617556 has been marked as a duplicate of this bug. ***
