On Tuesday 04 February 2003 07:31 pm, you wrote: > On Monday 03 February 2003 01:52 pm, you wrote: > > On Saturday 01 February 2003 02:37 pm, you wrote: > > > I heve already rebuilt most of my rpms for MAndrake9.1. > > > >The bug is called unresolved symbol, this bug exists in ALSA 0.9 since the > >existing of ALSA 0.9. > > > >I tried nearly every ALSA 0.9x version. > > Found this about alsa 0.9.x > > This "bug" is mostly causes by in-correct install of alsa. > In order to install alsa, you must first compile and install your own > kernel. > Once the kernel is installed and running, you can then compile and > install alsa-driver. > Once you have alsa-driver installed, with all the modules, you can then > compile and install alsa-lib. > Also, the kernel must be compiled with the same compiler as the alsa-driver > modules. E.g. You cannot have compiled the kernel with gcc 2.95 and compile > alsa-driver with gcc 3.2. Using different compilers causes all sorts of > strange un-predictable problems. I took a few days once tried to track down > a kernel oops, only to find that simply compiling both kernel and > kernel-module with the same compiler fixed the issue. > That should solve all "unresolved symbols". > > Th kernel is dated jan 30 2003 > gcc dated jan 3.21 30 2003 > and libalsa jan 10 2003 > > so this is not going to work!!!! > > /thac
This deals with my problem to load the alsa driver. Is the kernel really built with the latest gcc ? obviously tha alsa libs aint. The other problem with muse seems to be autotools related. the strange thing is that it builds perfectly in 9.0. Im working on it now. /thac
