(#534) compiling problem (Mdk9.0 + alsa)

Message posted to the Speak Freely Forum
  by Ivan Nanov on Wed, 19 Nov 2003 21:58:16 +0100 (MET).
  http://www.fourmilab.ch/wb/speak-freely.pl?rev=534

Hi All,
I am running Mandrake 9.0 on Intel based PC - SOYO SY-K7VTA-B motherboard with
on-board AC97 codec. I am a Linux newbie trying to compile Speak Freely 7.6a
with ALSA. So far I have managed to fix some of the compiling errors, and now
I need some help.

I installed the following rpms,
libncurses5-devel-5.2-27mdk.i586.rpm and
libalsa2-devel-0.9.0-0.8rc2mdk.i586.rpm,
and made also some tests of the audio hardware:

[ivan@localhost test]$ rec junk.au
Send break (control-c) to end recording
sox: Unable to set audio speed to 8000 (set to 48000)
[ivan@localhost test]$ play junk.au
sox: Unable to set audio speed to 8000 (set to 48000)

rec and play commands work fine.

Next I changed the original Makefile as follows:
1) I added -lalsa in
LFLAGS = -lncurses -lm -lalsa
in order to fix a bunch of errors starting with:
audio_alsa.c:20:28: alsa/asoundlib.h: No such file or directory

2) Uncomment
CCFLAGS = -DLINUX_ALSA -DM_LITTLE_ENDIAN
SOUNDLIB = -lasound
as it is required for ALSA support.

The following is the list of errors I got:

audio_alsa.c: In function `soundinit_2':
audio_alsa.c:146: warning: passing arg 3 of `snd_pcm_hw_params_set_rate_near'
makes integer from pointer without a cast
audio_alsa.c:163: warning: passing arg 3 of
`snd_pcm_hw_params_set_buffer_time_near' makes integer from pointer without a
cast
audio_alsa.c:168: warning: passing arg 3 of
`snd_pcm_hw_params_set_period_time_near' makes integer from pointer without a
cast
audio_alsa.c:179: warning: passing arg 2 of
`snd_pcm_hw_params_get_period_size' from incompatible pointer type
audio_alsa.c:179: too many arguments to function
`snd_pcm_hw_params_get_period_size'
audio_alsa.c:180: too many arguments to function
`snd_pcm_hw_params_get_buffer_size'
audio_alsa.c:196: too many arguments to function
`snd_pcm_sw_params_get_xfer_align'
make: *** [audio_alsa.o] Error 1

I don't think, I have a capacity to dig inside the C code. If someone has
experienced the same problem or knows how to fix it, please reply. Any help
will be highly appreciated.


                      * * *

To unsubscribe from this mailing list, send E-mail containing
the word "unsubscribe" in the message body (*not* as the
Subject) to [email protected]