At Mon, 25 Jun 2007 23:32:39 +0100, Adrian McMenamin wrote:
You can check ldd to the app which shlib it's linked with. It should be linked with libsalsa, not libasound.
Takashi
I expect I am being a bit thick here but what app? I use mpg123 and it's not linked with any alsa libs.
/ # ldd ./mpg123 libm.so.0 => /lib/libm.so.0 (0x2956d000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x2958b000) libc.so.0 => /lib/libc.so.0 (0x295aa000) ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x29558000)
mpg123 is an OSS app.
/ # ldd aplay libasound.so.2 => /usr/lib/libasound.so.2 (0x2956d000) libm.so.0 => /lib/libm.so.0 (0x29652000) libdl.so.0 => /lib/libdl.so.0 (0x29670000) libpthread.so.0 => /lib/libpthread.so.0 (0x29683000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x296a4000) libc.so.0 => /lib/libc.so.0 (0x296c3000) ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x29558000)
It's liekly linked with the old libasound.
SALSA-lib is a source-level compatible library and it's _not_ binary-level compatible. Thus, it's no drop-in replacement. After installing salsa-lib (better use --enable-everything option to make a libasound symlink), then you'll have to rebuild the other apps linked with alsa-lib again.
Takashi