Jaroslav Kysela <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED]:~/alsa/alsa-lib/test> make pcm > [...] > [EMAIL PROTECTED]:~/alsa/alsa-lib/test> ./pcm > [...] > Using transfer method: write > > So, what's your problem?
Notice that I relinked pcm dynamically to make it run. However: tba:/usr/local/src/alsa-lib-0.9.8/test/ $ make pcm source='pcm.c' object='pcm.o' libtool=no \ depfile='.deps/pcm.Po' tmpdepfile='.deps/pcm.TPo' \ depmode=gcc /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -static -Wall -pipe -g -c `test -f pcm.c || echo './'`pcm.c /bin/sh ../libtool --mode=link gcc -static -Wall -pipe -g -o pcm pcm.o ../src/libasound.la mkdir .libs gcc -Wall -pipe -g -o pcm pcm.o ../src/.libs/libasound.a -lm -ldl -lpthread tba:/usr/local/src/alsa-lib-0.9.8/test/ $ ./pcm Playback device is plughw:0,0 Stream parameters are 44100Hz, S16_LE, 1 channels Sine wave rate is 440.0000Hz Using transfer method: write device='plughw:0,0', stream=0, open_mode=0 ALSA lib pcm.c:1876:(snd_pcm_open_conf) symbol _snd_pcm_plug_open is not defined inside (null) Playback open error: No such device or address I added the fprintf("device=...") to the code. $ libtool --version ltmain.sh (GNU libtool) 1.5.0a (1.1220.2.35 2003/11/12 18:51:58) Debian: 179 $ Notice that I'm compiling Debian Sid sources, don't run these myself: Makefile.in # Makefile.in generated automatically by automake 1.5 from Makefile.am. $ automake --version automake (GNU automake) 1.6.3 configure: # Generated by Autoconf 2.52. $ autoconf --version autoconf (GNU Autoconf) 2.59 As a side question, should these "ALSA lib..." error messages be reported from every application which links to Alsa? Or must they be enabled or similar? I'm struggling with Glame, in which snd_pcm_open returns Illegal arguments in a similary trivial call, but I can't see ALSA lib messages in the output. Feri. ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel