Re: Compiling problems :S

On 18/07/06 15:07, Jordi Vendrell wrote:
> 
> Thanks a lot, using gcc-2.95 worked well...
> except for these lines in the make log
> 
> depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/8255.o
> depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/adl_pci9118.o
> depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/adv_pci1710.o
> depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/cb_pcidas.o
> depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/cb_pcidda.o
> depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/comedi.o
> depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/comedi_parport.o
> depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/das08.o
> depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/das16.o
> depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/das16m1.o
> depmod: *** Unresolved symbols in /lib/modules/2.2.19/misc/das1800.o
> (...)
> 
> Do you know if it is because I hadn't installed yet Comedilib, or for
> some other reason?
> Are they relevant, by the way? :S

It's nothing to do with Comedilib.  It could be one of two reasons:

1. There may be a mismatch between the kernel configuration options
(.config) used to build the kernel and those used to build the Comedi
modules.

2. The Comedi modules may be trying to link to something not supported
by the 2.2.19 kernel.

You can run:

   depmod -ae

to find out which symbols are unresolved.

Which version of Comedi are you using for this?

-- 
-=( Ian Abbott _at_ MEV Ltd.    E-mail: <abbotti_at_mev.co.uk>        )=-
-=( Tel: +44 (0)161 477 1898   FAX: +44 (0)161 718 3587         )=-

Received on 2006-07-19Z12:11:13