| 1 |
On 11/06/2012 04:18 PM, Frank Steinmetzger wrote: |
| 2 |
> Hello |
| 3 |
> |
| 4 |
> For everything there is a first time. So after years of coping by myself, |
| 5 |
> this is the first time I need an advice on a shared libary that can't be |
| 6 |
> found. My problem: |
| 7 |
> |
| 8 |
> $ ams |
| 9 |
> ams: error while loading shared libraries: libclalsadrv.so.1: cannot open |
| 10 |
> shared object file: No such file or directory |
| 11 |
> |
| 12 |
> I ran revdep-rebuild -pvi twice, the result was that only ams needs to be |
| 13 |
> rebuilt. So I did it. But because it didn't solve the problem, I ran revdep |
| 14 |
> again with the same outcome, |
| 15 |
|
| 16 |
My theory is that ams is linked to some library that is still linked to the |
| 17 |
missing one, i.e. ams has an indirect dependency through an old library that |
| 18 |
needs to be rebuilt --but-- for some reason revdep is not finding it. (Don't |
| 19 |
ask me why ;) |
| 20 |
|
| 21 |
I highly recommend the lddtree utility for tracking down indirect dependency |
| 22 |
like that. It is part of app-misc/pax-utils, which includes other interesting |
| 23 |
utilities that I don't yet know how to use. |
| 24 |
|
| 25 |
Even if it doesn't find your problem it's still worth every penny you pay |
| 26 |
for it :) |
Archives