With my use flags, it summarises its configuration thus: Configuration: Install path: /usr Use libmad shared library: yes Enable libid3tag support: yes Build GTK interface: yes Build OpenGL based visual plugins: yes Build alsa 0.5.x output plugin: yes Build alsa 0.9.x output plugin: no Build jack output plugin: no Build oss output plugin: yes Build esound output plugin: no Build sparc output plugin: no Build sgi output plugin: no Build nas output plugin: yes Build vorbis input plugin: yes Build mikmod input plugin: yes Build audiofile input plugin: no Build flac input plugin: no Then it compiles a few output modes (gtk, text) before it tries to compile the alsa 0.5.x plugin: make[3]: Entering directory `/var/tmp/portage/alsaplayer-0.99.70-r1/work/alsaplayer-0.99.70/output/alsa-0.5.x' make[3]: *** No rule to make target `alsa_out.c', needed by `alsa_out.lo'. Stop. make[3]: Leaving directory `/var/tmp/portage/alsaplayer-0.99.70-r1/work/alsaplayer-0.99.70/output/alsa-0.5.x' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/alsaplayer-0.99.70-r1/work/alsaplayer-0.99.70/output' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/var/tmp/portage/alsaplayer-0.99.70-r1/work/alsaplayer-0.99.70' That apparently fails. I cannot upgrade to newer alsa drivers, as they don't support my card (intel8x0 drivers). I have tried nagging the alsa-user list for input on this, but nothing came out of it. In fact, the alsa 0.5.x drivers don't work on the 2.4.18 and 2.4.19 kernels with the intel sound card at all. The kernel OSS driver just oopses on load with 2.4.18 and 2.4.19.
Karl, According to Andy, the upstream author: This bug has also been fixed in CVS, so consider it closed when the next release comes out. I did a replace operation in the Makefile.am file at one point and inadvertently mangled the source file name of the alsa-0.5 output plugin. So, I guess we wait for the new version to come out, or I can resurrect the older version of the player for you from our cvs attic. Your choice..
If I am the only user of alsaplayer that experiences this problem, we wait.
I have uploaded a CVS snapshot of alsaplayer, which sorts this issue out. Also, I have fixed the ebuild to work with nas.