Am 23.01.2012 23:03, schrieb walt: > On 01/23/2012 05:25 AM, Mervyn Hammer wrote: >> Would anyone be able to help me understand the following curiosity? >> >> I installed =net-analyzer/netcat-110-r8 (USE="crypt ipv6 -static") >> without apparent problem but running it produced: >> >> "nc: error while loading shared libraries: libmix.so.0: cannot open >> shared object file: No such file or directory." >> >> A quick check of emerge.log showed dev-libs/libmix-2.05-r5 installed >> without error, so I ran a deep world update followed by a --depclean >> and revdep-debuild: revdep-rebuild identified a broken dependency >> for netcat and reinstalled it automatically (same version), stating >> that the breakage had been rectified. Re-running revdep-rebuild, >> however, revealed that the problem still existed. I unmerged both >> libmix and netcat and re-emerged them (libmix first). Neither >> complained and logs show nothing of note. After unmerging and >> re-emerging both libmix and netcat (libmix first) revdep-rebuild no >> longer found a broken dependency for netcat. Still, however, netcat >> gave the same error (above). I temporarily "fixed" the problem by >> creating a symlink (/usr/lib/libmix.so.0 -> /usr/lib/libmix.so) >> to give netcat what it says it is looking for but this feels like a hack >> for some that I would presume should work cleanly by design. > Very strange indeed. I just installed both packages and I have no > libmix.so.0 either, yet everything works. > > No idea what's causing your problem, but I agree it's a problem I'd > want to solve. I'd try running ldconfig -p and lddtree /usr/bin/nc > to see where the .0 is coming from. (lddtree is from pax-utils). I ran into this problem some time ago, it seems the ebuild dev-libs/libmix-2.05-r5 is broken. It does no longer create a symlink from libmix.so.0 to libmix.so.
I found two solutions: 1. Creating the symlink manually 2. Using the unstable version of libmix, dev-libs/libmix-2.05-r6, the problem disappears because the programs (as soon as they are recompiled) directly link against libmix.so. The symlink won't be created either, but is unnecessary with this version. I chose the second option, first upgrading libmix and afterwards revdep-rebuild (in my case, it detected the problem, otherwise just reemerge netcat). Maybe it would be a good idea to stable the new libmix version... Regards, Felix
