| 1 |
On Tue, 06 Nov 2012 17:56:12 -0800 |
| 2 |
walt <w41ter@×××××.com> wrote: |
| 3 |
|
| 4 |
> On 11/06/2012 04:18 PM, Frank Steinmetzger wrote: |
| 5 |
> > Hello |
| 6 |
> > |
| 7 |
> > For everything there is a first time. So after years of coping by |
| 8 |
> > myself, this is the first time I need an advice on a shared libary |
| 9 |
> > that can't be found. My problem: |
| 10 |
> > |
| 11 |
> > $ ams |
| 12 |
> > ams: error while loading shared libraries: libclalsadrv.so.1: |
| 13 |
> > cannot open shared object file: No such file or directory |
| 14 |
> > |
| 15 |
> > I ran revdep-rebuild -pvi twice, the result was that only ams needs |
| 16 |
> > to be rebuilt. So I did it. But because it didn't solve the |
| 17 |
> > problem, I ran revdep again with the same outcome, |
| 18 |
> |
| 19 |
> My theory is that ams is linked to some library that is still linked |
| 20 |
> to the missing one, i.e. ams has an indirect dependency through an |
| 21 |
> old library that needs to be rebuilt --but-- for some reason revdep |
| 22 |
> is not finding it. (Don't ask me why ;) |
| 23 |
> |
| 24 |
> I highly recommend the lddtree utility for tracking down indirect |
| 25 |
> dependency like that. It is part of app-misc/pax-utils, which |
| 26 |
> includes other interesting utilities that I don't yet know how to use. |
| 27 |
> |
| 28 |
> Even if it doesn't find your problem it's still worth every penny you |
| 29 |
> pay for it :) |
| 30 |
> |
| 31 |
|
| 32 |
If that proves to be the correct solution, I highly recommend telling |
| 33 |
flameyes all about it. |
| 34 |
|
| 35 |
He'll rant and rave on his blog at length, completely describing all |
| 36 |
the details and problems that you really don't want to know about. |
| 37 |
|
| 38 |
And shortly thereafter he'll have a most elegant solution to the entire |
| 39 |
root problem that just fixes it and never comes up again. |
| 40 |
|
| 41 |
He's good that way :-) |
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
-- |
| 46 |
Alan McKinnon |
| 47 |
alan.mckinnon@×××××.com |
Archives