From: Chris B. <ch...@cn...> - 2004-11-22 04:47:43
|
On Sun, Nov 21, 2004 at 06:08:04PM -1000, Jimen Ching wrote: > I wonder if there's a cleaner way of checking for ALSA. I noticed that > alsa-lib keeps its own asound.h header file. This looks suspiciously like > glibc (maintaining its own kernel headers). Off hand, I think I prefer possible compile failures over trying to debug user reports that may be sox bugs or may be incompatible asound.h header files without any way of knowing the difference. > I've downloaded the alsa-lib source code and took a look at how it > re-solved this __user/__kernel problem. In version 1.0.6, the asound.h > file doesn't use either of these macros. Which version are you using? My sound/version.h says 1.0.6 but this is from the 2.6.9 kernel.org kernel. Also, Fedora Core 3 has same kernel and problems. Both asound.h's include at least a reference to __user that is failing to compile. So it sounds like alsa-lib just has a non-kernel version of asound.h that they've stripped out the __user and __kernel references? For now, my hack to define __user and __kernel to nothing seems reasonable (same outcome as keeping a local copy of asound.h anyways). BTW, I getting ready to modify play.in so that it understands that OSS and/or ALSA is compiled in and then selects the appropriate driver (giving preference to ALSA if both exist). See any issues with doing this? Chris |