[Pkg-alsa-devel] building alsa-plugins fails w/ libasound has no external plugin SDK
Darren Hart
darren at dvhart.com
Sat Dec 13 19:58:57 UTC 2008
On Sat, Dec 13, 2008 at 9:36 AM, Elimar Riesebieter <riesebie at lxtec.de> wrote:
> * Darren Hart [081213 17:20 +0100]
> [...]
>> I found config.log in bibuild, but nowhere else... Checking it, the
>> apparently relevant section complains about my installed libasound
>> libs being "incompatible". The alsa-utils and alsa-tools packages
>> were able to use the ok...
>>
>
> What tells:
> $ dpkg -l | grep asound
>
$ dpkg -l | grep asound
ii lib32asound2 1.0.18-1
shared library for ALSA applications (32 bit
ii lib32asound2-dev 1.0.18-1
shared library for ALSA applications -- deve
ii libasound2 1.0.18-1
shared library for ALSA applications
ii libasound2-dev 1.0.18-1
shared library for ALSA applications -- deve
ii libasound2-doc 1.0.18-1
developer documentation for user-space ALSA
and lib32asound2 installs the library here:
/emul/ia32-linux/usr/lib/libasound.so.2.0.0
And this file also appears to have the symbol in question:
$ objdump -T /emul/ia32-linux/usr/lib/libasound.so.2.0.0 | grep ioplug_create
00090340 g DF .text 000001f0 ALSA_0.9 snd_pcm_ioplug_create
Does the alsa-plugins build need to be lookoing there for the bibuild?
--
Darren Hart
More information about the Pkg-alsa-devel
mailing list