Re: [Alsa-user] modprobe - unresolved symbols in snd.o
Brought to you by:
perex
From: Paul S. <so...@us...> - 2002-09-14 06:38:46
|
Ok - I can find my way around makefiles and gcc but there is so much damn indirection. The utils/config.log doesn't actually indicate where it thought it was and I can't find a verbose option for configure. - The kernel and kernel source were installed directly from rpms (fresh from redhat). - I didn' t set any ./configure options in driver/lib/utils. - According to alsa-utils/configure --help the prefix defaults to /usr. - alsa-lib/Makefile has "prefix = /usr" - alsa-driver/Makefile.conf has "prefix = /usr" - libasound.so is in /usr/lib (along with various links related to it). sosman ----- Original Message ----- From: "Fedor G. Pikus" <fe...@wv...> To: "Paul Sorenson" <so...@us...> Sent: Saturday, September 14, 2002 1:54 PM Subject: Re: [Alsa-user] modprobe - unresolved symbols in snd.o > Sounds to me like you used non-standard prefixes when you configure'd > alsa-lib. The makefiles are not entirely correct for these situations, > you may have to hack them manually after running ./configure if you > want to use non-standard prefixes. It's not hard to do if you know gcc > command line options and Makefile syntax, but if you don't, it's hard for > me to tell you exactly what to do because the way in which this stuff > breaks changes from release to release :) > > What you should be able to do is install in standard locations. > cd alsa-drivers > ./configure > make > make install > cd ../alsa-libs > ./configure > make > make install <---- you have to do this before you go build utils! > cd ../alsa-utils > ./configure > make > make install > > > If you used --prefix but did not do the above steps in the correct order, > then try them first with your prefix and in the correct order, then give > up on the prefix, remove your alsa stuff from non-standard locations you > had it installed, and install it where it likes to be installed. > > Fedor > > > On Sat, 14 Sep 2002, Paul Sorenson wrote: > > > > Fedor, > > > > Thanks again. > > > > modversions.h was indeed missing. After searching around for the source rpm > > on my system (I use up2date for updates and I am not sure how long > > downloaded packages are cached for) I just ran up2date again because the > > updates included 2.4.18-10 (and I chose only the athlon and source > > packages). > > > > After installing the new kernel and source the driver compiled no problems > > and modprobe snd-ens1371 went without a hitch. > > > > I can run alsaplayer with no errors. There is no sound so I am currently > > trying to unmute. Unfortuately the ./configure in alsa-utils barfed with > > the error "no linkable libasound was found", in actual fact it appears in > > /var/lib and running ./configure --libdir=/var/lib resulted in the same > > error. Without being able to compile the utils I am not sure how to unmute > > (KMix won't run anymore). > > > > sosman > > > > > > ----- Original Message ----- > > From: "Fedor G. Pikus" <fe...@wv...> > > To: "Paul Sorenson" <so...@us...> > > Sent: Friday, September 13, 2002 2:28 AM > > Subject: Re: [Alsa-user] modprobe - unresolved symbols in snd.o > > > > > > > This is an odd error to get. You are including > > > /usr/include/linux/modversions.h > > > when you should be including > > > /lib/modules/2.4.18-5/build/include/linux/modversions.h > > > > > > There can be only two explanations. > > > 1) Check that you have > > > /lib/modules/2.4.18-5/build/include/linux/modversions.h. It should contain > > > something like this: > > > #ifndef _LINUX_MODVERSIONS_H > > > #define _LINUX_MODVERSIONS_H > > > #include <linux/modsetver.h> > > > #include <linux/modules/53c700.ver> > > > .... lots of stuff > > > #endif > > > > > > If you do not have it, your kernel-source rpm is missing some files, > > > reinstall it. > > > If you do have it, something must be wrong in the results of .configure. > > > Remove your alsa-drivers directory, untar the tarball again (remove > > > isapnp.h as the web page says) and run .configure again (this is a bit too > > > drastic, you could probably just do make clean and remove config.cache, > > > config.log, and config.status). > > > > > > On Thu, 12 Sep 2002, Paul Sorenson wrote: > > > > > > > Date: Thu, 12 Sep 2002 18:09:20 +1000 > > > > From: Paul Sorenson <so...@us...> > > > > To: "Pikus, Fedor" <fed...@me...> > > > > Subject: Re: [Alsa-user] modprobe - unresolved symbols in snd.o > > > > > > > > Fidor, > > > > > > > > The bits and pieces. > > > > > > > > paul > > > > > > > > ----- Original Message ----- > > > > From: "Fedor G. Pikus" <fe...@wv...> > > > > To: "Paul Sorenson" <so...@us...> > > > > Cc: "alsa user" <als...@li...> > > > > Sent: Monday, September 09, 2002 4:25 PM > > > > Subject: Re: [Alsa-user] modprobe - unresolved symbols in snd.o > > > > > > > > > > > > > Hmm, hard to say. I compiled alsa 0.9rc3 against 2.4.18 Redhat kernel, > > > > > with Athlon config. > > > > > Could you post the output of "uname -a" and "ls -l /usr/src/"? > > > > > Also attach your /usr/src/linux/.config file (perhaps that one you > > can > > > > > send to me instead of the list, I want to diff it against mine to see > > if > > > > > there is something wrong there). > > > > > > > > > > > > > > -- > > > Fedor G. Pikus > > > Mentor Graphics Corporation | Phone: (503) 685-4857 > > > 8405 SW Boeckman Road | FAX: (503) 685-1239 > > > Wilsonville, Oregon 97070 | http://www.pikus.net/~pikus/ > > > > > > > -- > Fedor G. Pikus > Mentor Graphics Corporation | Phone: (503) 685-4857 > 8405 SW Boeckman Road | FAX: (503) 685-1239 > Wilsonville, Oregon 97070 | http://www.pikus.net/~pikus/ > |