[gentoo-user] Revdep-rebuild: ams won't start due to shared library libclalsadrv.so.1

[Frank Steinmetzger]

Hello

For everything there is a first time. So after years of coping by myself,
this is the first time I need an advice on a shared libary that can't be
found. My problem:

$ ams
ams: error while loading shared libraries: libclalsadrv.so.1: cannot open
shared object file: No such file or directory

I ran revdep-rebuild -pvi twice, the result was that only ams needs to be
rebuilt. So I did it. But because it didn't solve the problem, I ran revdep
again with the same outcome, so I built ams again. Next I did
$ qdepends libclalsadrv
The only returned packages was alsa-lib, so I did
$ emerge alsa-lib ams

Next I looked at the binary, and indeed it contains the string libclalsadrv.so.1.
But right before that, it mentions jack, so I also rebuilt jack (hope dies
last). But neither helped.

So, please help me remove the tomatoes from my eyes---what am I missing here?


Some background info:
$ eix -e -c ams -o libclalsadrv -o alsa-lib | sed 's_:.*__g'
[I] media-libs/alsa-lib (1.0....@07.11.2012)
[I] media-libs/libclalsadrv (1....@07.11.2012)
[I] media-sound/ams (2....@07.11.2012)

$ qlist libclalsadrv
/usr/share/doc/libclalsadrv-1.2.2/AUTHORS.bz2
/usr/include/clalsadrv.h
/usr/lib64/libclalsadrv.so
/usr/lib64/libclalsadrv.so.1.2.2

--
Gruß | Greetings | Qapla'
Please do not share anything from, with or about me with any Facebook service.

The four elements: earth, air and firewater.

[walt]

On 11/06/2012 04:18 PM, Frank Steinmetzger wrote:
> Hello
>
> For everything there is a first time. So after years of coping by myself,
> this is the first time I need an advice on a shared libary that can't be
> found. My problem:
>
> $ ams
> ams: error while loading shared libraries: libclalsadrv.so.1: cannot open
> shared object file: No such file or directory
>
> I ran revdep-rebuild -pvi twice, the result was that only ams needs to be
> rebuilt. So I did it. But because it didn't solve the problem, I ran revdep
> again with the same outcome,

My theory is that ams is linked to some library that is still linked to the
missing one, i.e. ams has an indirect dependency through an old library that
needs to be rebuilt --but-- for some reason revdep is not finding it. (Don't
ask me why ;)

I highly recommend the lddtree utility for tracking down indirect dependency
like that. It is part of app-misc/pax-utils, which includes other interesting
utilities that I don't yet know how to use.

Even if it doesn't find your problem it's still worth every penny you pay
for it :)

[Frank Steinmetzger]

On Tue, Nov 06, 2012 at 05:56:12PM -0800, walt wrote:

> > Hello
> > […]

> > $ ams
> > ams: error while loading shared libraries: libclalsadrv.so.1: cannot open
> > shared object file: No such file or directory
> >
> > I ran revdep-rebuild -pvi twice, the result was that only ams needs to be
> > rebuilt. So I did it. But because it didn't solve the problem, I ran revdep
> > again with the same outcome,
>
> My theory is that ams is linked to some library that is still linked to the
> missing one, i.e. ams has an indirect dependency through an old library that
> needs to be rebuilt --but-- for some reason revdep is not finding it. (Don't
> ask me why ;)

Mind you, the ams executable itself has the string for the missing library in
it. I suppose it’s an error in libclalsadrv, because it doesn’t install a *so.1
symlink.

> I highly recommend the lddtree utility for tracking down indirect dependency
> like that. It is part of app-misc/pax-utils, which includes other interesting
> utilities that I don't yet know how to use.

I’ve used that before on one or two occasions, but forgot all about it already.

$ lddtree /usr/bin/ams
ams => /usr/bin/ams (interpreter => /lib64/ld-linux-x86-64.so.2)
libdl.so.2 => /lib64/libdl.so.2
libQtGui.so.4 => /usr/lib64/qt4/libQtGui.so.4
[...]
libQtCore.so.4 => /usr/lib64/qt4/libQtCore.so.4
[...]
libpthread.so.0 => /lib64/libpthread.so.0
libjack.so.0 => /usr/lib64/libjack.so.0
libclalsadrv.so.1 => not found
[...]

> Even if it doesn't find your problem it's still worth every penny you pay
> for it :)

In this particular case I am glad I didn’t pay a penny or a dime. :-p

--
Gruß | Greetings | Qapla'
Please do not share anything from, with or about me with any Facebook service.

He always hits the nail on the thumb.

[walt]

On 11/07/2012 04:08 AM, Frank Steinmetzger wrote:
> On Tue, Nov 06, 2012 at 05:56:12PM -0800, walt wrote:
>
>>> Hello
>>> […]
>>> $ ams
>>> ams: error while loading shared libraries: libclalsadrv.so.1: cannot open
>>> shared object file: No such file or directory
>>>
>>> I ran revdep-rebuild -pvi twice, the result was that only ams needs to be
>>> rebuilt. So I did it. But because it didn't solve the problem, I ran revdep
>>> again with the same outcome,
>>
>> My theory is that ams is linked to some library that is still linked to the
>> missing one, i.e. ams has an indirect dependency through an old library that
>> needs to be rebuilt --but-- for some reason revdep is not finding it. (Don't
>> ask me why ;)

> Mind you, the ams executable itself has the string for the missing library in
> it.

readelf -d is another way of finding such strings, maybe a little more elegant
than grep, though I use both.

> I suppose it’s an error in libclalsadrv, because it doesn’t install a *so.1
> symlink.

Ah, well, you didn't tell me that. Withholding evidence! :p

[Frank Steinmetzger]

On Wed, Nov 07, 2012 at 05:44:07AM -0800, walt wrote:

> > I suppose it’s an error in libclalsadrv, because it doesn’t install a *so.1
> > symlink.
>
> Ah, well, you didn't tell me that. Withholding evidence! :p

In fact I did; right at the bottom of the OP.

--
Gruß | Greetings | Qapla'
Please do not share anything from, with or about me with any Facebook service.

There are people who can reconstruct their family tree
back to those who still sat on it.

[Alan McKinnon]

If that proves to be the correct solution, I highly recommend telling
flameyes all about it.

He'll rant and rave on his blog at length, completely describing all
the details and problems that you really don't want to know about.

And shortly thereafter he'll have a most elegant solution to the entire
root problem that just fixes it and never comes up again.

He's good that way :-)



--
Alan McKinnon
alan.m...@gmail.com

[Frank Steinmetzger]

On Wed, Nov 07, 2012 at 01:08:37PM +0100, Frank Steinmetzger wrote:
> On Tue, Nov 06, 2012 at 05:56:12PM -0800, walt wrote:
>
> > > Hello
> > > […]
> > > $ ams
> > > ams: error while loading shared libraries: libclalsadrv.so.1: cannot open
> > > shared object file: No such file or directory

> > […]
> […]


Summarising:

$ lddtree /usr/bin/ams
ams => /usr/bin/ams (interpreter => /lib64/ld-linux-x86-64.so.2)

[...]

libclalsadrv.so.1 => not found
[...]

$ qlist libclalsadrv
/usr/share/doc/libclalsadrv-1.2.2/AUTHORS.bz2
/usr/include/clalsadrv.h
/usr/lib64/libclalsadrv.so
/usr/lib64/libclalsadrv.so.1.2.2

I’d like to file a bug report. But which one is the culprit in your opinion;
libclalsadrv for not providing a .so.1 link, or ams for stubbornly referencing
it in its executable? Of course the ams build log simply says for the linking:

x86_64-pc-linux-gnu-g++ ... -lclalsadrv ...

I’m just asking because I have a habit of making a fool of myself by reporting
stuff that turned out to be my own mistake or missing the point by a mile. :-/

--
Gruß | Greetings | Qapla'
Please do not share anything from, with or about me with any Facebook service.

I used to be vain, but now I know that I am beautiful.