Why don't you create a link called modversions.h that points to version.h? Best regards, Adrian ----- Original Message ----- From: "Joachim v. Jena" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, June 25, 2003 12:48 AM Subject: Alsa 0.94 installation Re: [expert] Make xconfig doesn't work in new kernel
> James Sparenberg wrote: > > > On Sun, 2003-06-15 at 02:27, Joerg Mertin wrote: > > > >>James Sparenberg wrote: > >> > >>>On Sat, 2003-06-14 at 20:52, Greg Meyer wrote: > >>> > >>> > >>>>On Saturday 14 June 2003 11:49 pm, James Sparenberg wrote: > >>>> > >>>> > >>>> > >>>>>I've had this for a while on all kernels with my hardware. I just vi > >>>>>.config and search for asm or ASM every time I find it I comment the > >>>>>line out with a #. Then it compiles. Seems that ASM can only compile > >>>>>on boxes that need/use it I guess. OR there is something else that > >>>>>needs a yes or module that isn't obvious. > >>>>> > >>>> > >>>>I got it done by using make oldconfig, but I suppose it should work. I also > >>>>just got dumped out of menuconfig when I tried to enter the ALSA > >>>>configuration. I suppose I should report both of these to vdanen. > >>> > >>>xconfig works ok if you can use it. > >> > >>Talking about Alsa, > >> > >>you can download the new alsa 0.9.4 drivers if you want. Just make sure > >>- during compile time you disable the verbose-printk with > >>./configure --disable-verbose-printk > >> > >>if not - you'll get failed dependencies on snd.o which makes the entire > >>soundsystem unusable. > >> > >>Cheers > >> > >> Joerg > > It seems common wisdom in this group that make menuconfig > crashes when selecting an alsa-driver. > > I tried to follow Joerg's hints to avoid these problems. I > have the kernel 2.4.21-0.18mdk installed and the > kernel-sources 2.4.21-0.18mdk as well. > > My question: > > 1) Is it sufficient to install the alsa 0.94 driver-package > alone from www.alsa-project.org > to circumvent/resolve the alsa problems? > > 2) Has anyone besides Joerg tried his method successfully? > > ./configure --disable-verbose-printk > > worked. > > But then the following make failed on the first occurrence of an > > #include <linux/modversions.h> > > in some source file. The first one where this happened, was > > ./support/pnp/pnp.c > > I began with hacking this file without knowing of what is > going on. > > I replaced > > > /* > * #include <linux/modversions.h> > */ > > by > > #include > "/lib/modules/2.4.21-0.18mdk/build/include/linux/version.h" > > according to the error message. This seemed to work. > But now the same error reappeared on compiling the next file > containing > > #include <linux/modversions.h>, > > which is ./acore/memalloc.inc, and stops the build process > thereafter. > > A find/grep shows that > > ./acore/memalloc.inc > ./acore/memory_wrapper.c > ./acore/sgbuf.c > ./acore/wrappers.c > ./include/adriver.h > ./pci/rme9652/hammerfall_mem.inc > ./support/isapnp/isapnp.c > ./support/isapnp/isapnp_proc.c > ./support/isapnp/isapnp_quirks.c > ./support/pnp/pnp.c > ./usb/usbcompat.c > > are all files containing an > > #include <linux/modversions.h> > > line. > > Because I don't believe that replacing > > #include <linux/modversions.h> > > by > > #include > "/lib/modules/2.4.21-0.18mdk/build/include/linux/version.h" > > in each of these files is the correct method to proceed I > stopped installing the alsa driver package. > > I would appreciate any comments. > > Joachim > > > > > > > ---------------------------------------------------------------------------- ---- > Want to buy your Pack or Services from MandrakeSoft? > Go to http://www.mandrakestore.com >
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
