Mr. Asselin,
I had similar problems before I did a 'make mrproper' in my Linux
directory before building the kernel. Then you must be certain to reboot
that kernel before building RTLinux. You can do a 'make clean' in the
RTLinux directory to start over with the RTLinux build once you are certain
you are running the right kernel.
I am not really sure what the 'make mrproper' does, but I do know
that it often (always?) resolves these unexpected unresolved symbol issues.
Regards,
Steve
> -----Original Message-----
> From: Maxime Asselin [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 02, 2001 11:15 AM
> To: [EMAIL PROTECTED]
> Subject: [rtl] Please help, unresolved symbols in RTLinux modules
>
>
> Please help, I have unresolved symbols in RTLinux modules
> since I upgraded
> to RTLinux 3.0 final.
>
> Linux kernel: 2.2.18 (fresh and clean archive)
> RTLinux: 3.0 final
>
> Included most common options in kernel from my saved config
> file I used with
> previous RTLinux releases.
> And I get:
>
> # depmod -ae
> depmod: *** Unresolved symbols in /lib/modules/2.2.18-rtl/misc/mbuff.o
> depmod: remap_page_range
> depmod: misc_deregister
> depmod: kmalloc
> depmod: create_proc_entry
> depmod: vfree
> depmod: kfree
> depmod: misc_register
> depmod: vmalloc
> depmod: remove_proc_entry
> depmod: mem_map
> depmod: sprintf
> depmod: init_mm
> depmod: printk
> depmod: __generic_copy_to_user
> depmod: *** Unresolved symbols in /lib/modules/2.2.18-rtl/misc/psc.o
> depmod: force_sig
> depmod: kmalloc
> depmod: create_proc_entry
> depmod: sys_call_table
> depmod: pidhash
> depmod: kfree
> depmod: remove_proc_entry
> depmod: proc_root
> depmod: sprintf
> depmod: *** Unresolved symbols in /lib/modules/2.2.18-rtl/misc/rtl.o
> depmod: vsprintf
> depmod: free_irq
> depmod: console_drivers
> depmod: request_irq
> depmod: __start_rtlinux_funcs
> depmod: printk
> depmod: *** Unresolved symbols in
> /lib/modules/2.2.18-rtl/misc/rtl_fifo.o
> depmod: __wake_up
> depmod: __generic_copy_from_user
> depmod: unregister_chrdev
> depmod: register_chrdev
> depmod: vfree
> depmod: interruptible_sleep_on_timeout
> depmod: __pollwait
> depmod: vmalloc
> depmod: xtime
> depmod: printk
> depmod: __generic_copy_to_user
> depmod: *** Unresolved symbols in
> /lib/modules/2.2.18-rtl/misc/rtl_posixio.o
> depmod: _ctype
> depmod: iounmap
> depmod: __ioremap
> depmod: simple_strtoul
> depmod: printk
> depmod: *** Unresolved symbols in
> /lib/modules/2.2.18-rtl/misc/rtl_sched.o
> depmod: kmalloc
> depmod: kfree
> depmod: tq_scheduler
> depmod: printk
> depmod: *** Unresolved symbols in
> /lib/modules/2.2.18-rtl/misc/rtl_time.o
> depmod: boot_cpu_data
> depmod: do_gettimeofday
> depmod: del_timer
> depmod: do_gettimeoffset
> depmod: use_tsc
> depmod: tick
> depmod: jiffies
> depmod: add_timer
> depmod: kd_mksound
>
> I am still able to load them in the kernel.
> And my RT modules work fine but still, I would like to know
> why these module
> dependencies errors occur.
>
>
> -- [rtl] ---
> To unsubscribe:
> echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
> echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
> --
> For more information on Real-Time Linux see:
> http://www.rtlinux.org/rtlinux/
>
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
--
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
