RE: [Alsa-user] Problem Installing ALSA 0.9.1 on Redhat 7.0--unresolved symbol
Brought to you by:
perex
From: RKHenry <rob...@ea...> - 2005-03-21 13:00:32
|
Clemens Ladisch wrote, > > One problem with using a newer version of ALSA is that on Redhat > > 7.0 the compiler used to compile the kernel, egcs 2.91.66, AKA > > KGCC, is not the compiler normally used for compiling ALSA, gcc > > 2.96. ALSA 1.0.8 checks for this and refuses to configure. >=20 > And if it wouldn't check for this, your kernel might blow up when you > try to load the ALSA modules. (This check isn't there just to annoy > you. ;-) >=20 > The configure script allows specifiying the compiler to use in the > usual way, i.e.: >=20 > CC=3Dmygcc ./configure --other-parameters... >=20 > > When I attempt to insert the module, I get these error messages: > > > > # modprobe snd-sscape > > snd-sscape.o: unresolved symbol snd_cs4231_... >=20 > Should be fixed now. Thank you very much, I'll try that. I've been just about ready to give = up and abandon the project. In a related question: I'm working on a programming project where I'm developing an application that needs sound. I have the option of = developing with OSS or stepping into the future and developing it with ALSA. Good choice or not? On the one hand I can save the added development time of fighting with installing ALSA, on the other hand it's generally = preferable to go with new technology rather than sticking with deprecated stuff. Opinions? I'd hoped to install ALSA on this machine so I could experiment with it = as a development machine. My difficulties in installing ALSA have made me = wonder if ALSA was a good choice. Is ALSA always this tough? Is installing it = on the target machines going to be another hurdle? Robert Henry |