Log in

No account? Create an account
LogJam [entries|archive|friends|userinfo]

[ website | LogJam ]
[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

[Sep. 19th, 2004|11:48 pm]


I am using logjam 4.3.2 on Gentoo, and recently removed my ALSA libraries (it turned out that my audio card is currently better supported by OSS). Since then, when I try to start it, I get the following error message:

logjam: error while loading shared libraries: libasound.so.2: cannot open shared object file: No such file or directory

and it fails to load. When I try to emerge it, in the hopes of it not building against libasound, the compile dies with

libtool: link: cannot find the library `/usr/lib/libasound.la'

Basically, what I want to know is whether logjam really depends on libasound in general or whether this is some weird Gentoo thing (or whether my system is just really screwed up).

[User Picture]From: fox2mike
2004-09-20 04:18 am (UTC)
Just Re-emergelogjam with emerge logjam

This is prolly a case of LogJam being built with ALSA support on Gentoo & since ALSA isn't there anymore...its can't find the library.

This should solve the issue...
(Reply) (Thread)
[User Picture]From: summerrose
2004-09-20 04:21 am (UTC)
Err, I have tried re-emerging it. In my post, I gave the error message that occurs when I try to re-emerge it.
(Reply) (Parent) (Thread)
[User Picture]From: hilker
2004-09-20 04:29 am (UTC)
Have you tried doing a revdep-rebuild? It’s part of the app-portage/gentoolkit package.
(Reply) (Parent) (Thread)
[User Picture]From: fox2mike
2004-09-20 04:30 am (UTC)
Whoops. Should have read more carefully.

How did you remove ALSA? libasound is part of alsa-libs.

You could try this :

1) Get Gentoolkit. emerge gentoolkit
2) Run revdep-rebuild -p

See the package list, decide if rebuilding will help. if it will, just run revdep-rebuild

This should fix broken dependencies...

Google for your error message.
(Reply) (Parent) (Thread)
[User Picture]From: summerrose
2004-09-20 04:35 am (UTC)
By 'emerge unmerge alsa-lib' and the same for a few other alsa things.
(Reply) (Parent) (Thread)
[User Picture]From: cheesetruck
2004-09-20 09:57 am (UTC)
Just because it sounds like something still believes ALSA IS there, you might try an

emerge -pv system

and see what comes back. (the -p is 'pretend', for those who don't know (not neccesarily the original poster.))

It may indicate quite a bit needs to be rebuilt - which is probably the case due to ALSA very possibly being linked into many base libraries.

However, it may come back and indicate everything is up to date. In which case, I'd check your USE flags to be sure it doens't specify ALSA support.

Are any other apps giving you fits?
(Reply) (Parent) (Thread)
From: geekosaur
2004-09-20 05:23 am (UTC)
I expect the real dependency is logjam->Gtk+->esound->ALSA (possibly with other dependencies in between, but esound->alsa would be the key one). Rebuilding esound (or whatever Gentoo package corresponds to esd/esound) should resolve it for logjam and other Gtk+-using packages.
(Reply) (Thread)
From: evan
2004-09-20 02:55 pm (UTC)
Generally, I find you get those sorts of errors when a libtool .la file is hanging around. It could be any library that logjam transitively depends on. LogJam itself doesn't depend on any sound libraries.

Two approaches:
- grep libasound.la /usr/lib/*.la, and then figure out what is still depending on asound;
- or just delete all the .la files in /usr/lib-- the GTK developers recommend this and you'll find your compiles speed up considerably. (.la files are needed on non-Linux systems but aren't necessary on Linux.)

Either way, there's the potential of a chained dependency like someone else mentioned, so be sure to back up any files you modify.
(Reply) (Thread)