I neglected to mention that the above patch (exactly the same, as it
turns out :-)) is how I forced the ide-proc.o build. The brokenness
extends deeper.
Specific example: proc_ide_read_geometry has the requisite EXPORT_SYMBOL()
wrapper in ide-proc.c, yet, I still end up with proc_ide_read_geometry_R*
unresolved at depmod time. In case anyone is wondering, I *did* do a
"make clean", manually cleaned out linux/include/modules to make *sure*
there wasn't any old cruft lying about, then ran "make dep && make bzImage &&
make modules && make modules_install". The depmod output quoted below is
the result of all that.
> if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.5.38; fi
> depmod: *** Unresolved symbols in /lib/modules/2.5.38/kernel/drivers/ide/ide-disk.o
> depmod: proc_ide_read_geometry_R50fed6f7
> depmod: *** Unresolved symbols in /lib/modules/2.5.38/kernel/drivers/ide/ide-floppy.o
> depmod: proc_ide_read_geometry_R50fed6f7
> depmod: *** Unresolved symbols in /lib/modules/2.5.38/kernel/drivers/ide/ide-probe.o
> depmod: do_ide_request
> depmod: ide_add_generic_settings
> depmod: create_proc_ide_interfaces_Rab2c600e
> depmod: ide_bus_type
> depmod: *** Unresolved symbols in /lib/modules/2.5.38/kernel/drivers/ide/ide.o
> depmod: proc_ide_create_Ra8e0f104
> depmod: ide_remove_proc_entries_R5a5a621b
> depmod: ide_add_proc_entries_Rce569c25
> depmod: destroy_proc_ide_drives_Ra54f63e5
> depmod: proc_ide_destroy_R35e1351c
> depmod: bus_unregister
> depmod: proc_ide_read_capacity_R46b2a30d
> depmod: create_proc_ide_interfaces_Rab2c600e
> depmod: ide_scan_pcibus
> make: *** [_modinst_post] Error 1
-- ----------------------------------------------------------------------- Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org rct@frus.com ----------------------------------------------------------------------- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/