Oh, I found the cause. My system is FC9 and alsa-lib is 1.0.16 while PA-dev tree requests 1.0.17 version. When I update alsa-lib to 1.0.17 the module-alsa-xxx.so comes back. I post it here for people who meet same issue. >-----Original Message----- >From: pulseaudio-discuss-bounces at mail.0pointer.de >[mailto:pulseaudio-discuss-bounces at mail.0pointer.de] On Behalf Of Zhang, Xing >Z >Sent: 2008?10?14? 9:50 >To: General PulseAudio Discussion >Subject: Re: [pulseaudio-discuss] Segmentation fault when load >module-alsa-sink by commandline > >I found below lines in src/Makefile >#am__append_35 = \ >#>-->---libalsa-util.la \ >#>-->---module-alsa-sink.la \ >#>-->---module-alsa-source.la > >This may be why there is no module-alsa-xxx.so produced. If I un-commented it, >a compiling error occurs with info "modules/alsa-util.c:29:23: error: >asoundlib.h: No such file or directory". But I really installed alsa-lib-devel >and asoundlib.h is actually at /usr/include/alsa/. Seems something wrong >happened when bootstrap.sh run. > >>-----Original Message----- >>From: pulseaudio-discuss-bounces at mail.0pointer.de >>[mailto:pulseaudio-discuss-bounces at mail.0pointer.de] On Behalf Of Zhang, >Xing >>Z >>Sent: 2008?10?13? 13:27 >>To: General PulseAudio Discussion >>Subject: Re: [pulseaudio-discuss] Segmentation fault when load >>module-alsa-sink by commandline >> >>> >>>Heya! >>> >>>> I am newbie to PA. Now I am trying to enable PA from scratch. When I >>>> enter "load-module module-alsa-sink" it complains "no such file >>>> found", then I launch PA with param "-p /usr/lib/pulse-0.9/modules/" >>>> unfortunately a segmentation fault happen while I load >>>> module-alsa-sink. I notice default.pa uses module-hal-detect instead >>>> of directly loading module-asla-xxx, so I want to know whether the >>>> issue I met is a known bug? Or any other methods to load >>>> module-alsa-xxx by manual? >>> >>>Hmm, do you mean you have compiled PA yourself? >>> >>>If you have to pass -p then this is probably a sign that your modules dir >>>and pa binary do not match: /usr/lib/pulse-0.9/modules probably >>>belongs to your installed version while your are running your own. >>> >>>Please note that the interface to the modules is not ABI or API stable >>>in any way. That means, if you load a module that was compiled for a >>>differnt PA version you will almost certainly get a segfault. >>> >>>If you want to run PA from your build tree then make sure to edit >>>~/.pulse/daemon.conf. There, set dl-search-path to something like this: >>> >>> dl-search-path = /home/lennart/projects/pulseaudio/src/.libs >>> >>>(This is the line I use, with having my GIT checkout of PA in >>>~/projects/pulseaudio. The .libs/ is especially important because >>>libtool puts its .so in that hidden subdir during build time) >>> >>>Hope this helps, >>> >> >>[Zhang, Xing Z] Thanks a lot. It's quite help! But I found there is no >>module-alsa-xxx.so at .libs/. Does PA remove it or I miss some compiling param >>to produce it? >>_______________________________________________ >>pulseaudio-discuss mailing list >>pulseaudio-discuss at mail.0pointer.de >>https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss >_______________________________________________ >pulseaudio-discuss mailing list >pulseaudio-discuss at mail.0pointer.de >https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
