On 03/20/2011 02:44 AM, Adam Carter wrote:
It looks like i've hit this issue; http://code.google.com/p/encfs/issues/detail?id=60So i've reinstalled boost 1.41 with; # emerge =boost-1.41.0-r3 # eselect boost set 1 # emerge encfs but its still broken, and $ ldd /usr/bin/encfs | grep boost libboost_serialization-mt-1_42.so.1.42.0 => /usr/lib64/libboost_serialization-mt-1_42.so.1.42.0 (0x00007fb6314de000) libboost_serialization-mt-1_41.so.1.41.0 => /usr/lib64/libboost_serialization-mt-1_41.so.1.41.0 (0x00007fb6305c5000) libboost_filesystem-mt-1_41.so.1.41.0 => /usr/lib64/libboost_filesystem-mt-1_41.so.1.41.0 (0x00007fb6303af000) libboost_system-mt-1_41.so.1.41.0 => /usr/lib64/libboost_system-mt-1_41.so.1.41.0 (0x00007fb6301ab000) So i'm assuming the problem is its still loading the v1.42 serialisation library. What's the correct way to that?
Some package on your machine is still linked against 1.42, though I can't tell you which one. Since you just rebuilt encfs, that isn't the guilty one. IMO the quickest way to find the package that needs rebuilding is:to move or rename libboost_serialization-mt-1_42.so.1.42.0, and then run ldd again and see who complains. Then rebuild the package that contains the complainer. I'm sure there are more elegant ways, but I think it should work.
