On Tuesday 24 Jan 2012 15:02, Mick wrote: > On Monday 23 Jan 2012 23:34:00 Mervyn Hammer wrote: >> Thanks for your replies. >> >>> Am 23.01.2012 23:03, schrieb walt: >>>> 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). >> For completeness: >> >> (for dev-libs/libmix-2.05-r5 after symlink created) >> >> ldconfig -p | grep libmix = >> >> libmix.so.0 (libc6) => /usr/lib/libmix.so.0 >> libmix++.so.0 (libc6) => /usr/lib/libmix++.so.0 >> >> and output from lddtree /usr/bin/nc = >> >> nc => /usr/bin/nc (interpreter => /lib/ld-linux.so.2) >> libmix.so.0 => /usr/lib/libmix.so.0 >> libc.so.6 => /lib/libc.so.6 >> >> * Felix Kuperjans <fe...@desaster-games.com> [2012-01-23 23:13:26 +0100]: >>> 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. >> Though it worked with the symlink, as you suggested, I upgraded libmix >> anyway. > > Hmm ... strange. > > I have dev-libs/libmix-2.05-r5 and I also have the symlink: > > $ ls -la /usr/lib64/libmix* > -rwxr-xr-x 1 root root 5752 Mar 25 2011 /usr/lib64/libmix++.so > lrwxrwxrwx 1 root root 11 Mar 25 2011 /usr/lib64/libmix++.so.0 -> > libmix++.so > -rwxr-xr-x 1 root root 98352 Mar 25 2011 /usr/lib64/libmix.so > lrwxrwxrwx 1 root root 9 Mar 25 2011 /usr/lib64/libmix.so.0 -> libmix.so This happens if a previous version created it.
Try unmerging libmix and netcat, delete the symlink and re-emerge netcat. It won't be created again, though it should. (At least, this happend on many of my boxes, x86 and amd64) Regards, Felix
