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