Re: [Alsa-user] Fedora 13: libasound where is the alsa.pc file located?

[John H. <jc...@th...>]

On 5 Jul 2010, at 20:35, Carlo Tambuatco wrote:

> I'm running Fedora 13, and I am trying to compile a program that
> requires libasound >=1.0 (which I have installed) but the ./configure
> file can't find it.
> 
> I've got
> 
> /lib/libasound.so.2
> /lib/libasound.so.2.0.0
> /usr/lib/alsa-lib/libasound_module_conf_pulse.so
> /usr/lib/alsa-lib/libasound_module_ctl_pulse.so
> /usr/lib/alsa-lib/libasound_module_pcm_pulse.so

You're missing alsa-devel -- just "yum install alsa-lib-devel".

In general, if you want to compile something that depends on a particular package you need the -devel version: in this case you want to compile against alsa-lib so you need to install alsa-lib-devel.

If you're not sure then "rpm -qf /lib/libasound.so.2" will tell you what that file belongs to (alsa-lib).  If you know what file you're looking for (eg .../libasound.so) then "yum whatprovides '*/libasound.so'" will tell you what you need to install (the wildcard is a good idea because it's actually /usr/lib/libasound.so, not what you might expect).

Your problem with jackbeat -- missing REG_EIP -- isn't quite so easy to sort out.  jackbeat-main is expecting that to be defined.   On my machine here you'd need to #include <ucontext.h> (probably) and jackbeat-main isn't.  That's not an alsa or jack problem :-)

jch