On Wed, Jan 19, 2005 at 02:48:08AM -0600, [EMAIL PROTECTED] wrote:
>                (cross posting this on kbuild-devel for some fresh light)
> The list of modules that Kbuild considers above appears to be limited to
> those built via the M= (or historically SUBDIRS=) argument, thus modpost
> doesn't know about the rest of the modules in the tree to consider for
> putting into depends:.  This is generic to all out-of-tree-built modules
> as I can tell, not necessarily just DKMS cross-arch builds.

As an example, if I do a 'make' from a top-level kernel directory, for
an in-tree build, modpost calls its read_symbols() with the whole list
of modules being built in-tree (debug printf added by me to demonstrate):
...
modpost: read_symbols(drivers/scsi/sata_sx4.o)
modpost: read_symbols(drivers/scsi/sata_via.o)
modpost: read_symbols(drivers/scsi/sata_vsc.o)
modpost: read_symbols(drivers/scsi/scsi_mod.o)
modpost: read_symbols(drivers/scsi/scsi_transport_fc.o)
modpost: read_symbols(drivers/scsi/scsi_transport_spi.o)
modpost: read_symbols(drivers/scsi/sd_mod.o)
modpost: read_symbols(drivers/scsi/sg.o)
modpost: read_symbols(drivers/scsi/sr_mod.o)
modpost: read_symbols(drivers/scsi/st.o)
modpost: read_symbols(drivers/scsi/sym53c8xx_2/sym53c8xx.o)
modpost: read_symbols(drivers/scsi/tmscsim.o)
modpost: read_symbols(drivers/usb/atm/speedtch.o)
modpost: read_symbols(drivers/usb/atm/usb_atm.o)
modpost: read_symbols(drivers/usb/class/cdc-acm.o)
modpost: read_symbols(drivers/usb/class/usb-midi.o)
modpost: read_symbols(drivers/usb/class/usblp.o)
modpost: read_symbols(drivers/usb/host/ehci-hcd.o)
modpost: read_symbols(drivers/usb/host/ohci-hcd.o)
modpost: read_symbols(drivers/usb/host/uhci-hcd.o)
modpost: read_symbols(drivers/usb/image/mdc800.o)
modpost: read_symbols(drivers/usb/image/microtek.o)
modpost: read_symbols(drivers/usb/input/aiptek.o)
modpost: read_symbols(drivers/usb/input/ati_remote.o)
modpost: read_symbols(drivers/usb/input/kbtab.o)
modpost: read_symbols(drivers/usb/input/mtouchusb.o)
modpost: read_symbols(drivers/usb/input/powermate.o)
modpost: read_symbols(drivers/usb/input/touchkitusb.o)
modpost: read_symbols(drivers/usb/input/wacom.o)
modpost: read_symbols(drivers/usb/input/xpad.o)
modpost: read_symbols(drivers/usb/media/dabusb.o)
modpost: read_symbols(drivers/usb/media/dsbr100.o)
...


But if I do the same thing out-of-tree using DKMS and M= notation, I
get only those modules built in the M= directory:

make: Entering directory `/home/mdomsch/bk/modinfo/linux-2.6-modinfo'
  LD      /var/lib/dkms/kernel_ppp_mppe/0.0.5/build/built-in.o
  CC [M]  /var/lib/dkms/kernel_ppp_mppe/0.0.5/build/ppp_generic.o
  CC [M]  /var/lib/dkms/kernel_ppp_mppe/0.0.5/build/ppp_mppe_compress.o
  CC [M]  /var/lib/dkms/kernel_ppp_mppe/0.0.5/build/sha1.o
  CC [M]  /var/lib/dkms/kernel_ppp_mppe/0.0.5/build/arcfour.o
  LD [M]  /var/lib/dkms/kernel_ppp_mppe/0.0.5/build/ppp_mppe.o
  Building modules, stage 2.
  MODPOST
modpost: read_symbols(vmlinux)
modpost: read_symbols(/var/lib/dkms/kernel_ppp_mppe/0.0.5/build/ppp_generic.o)
modpost: read_symbols(/var/lib/dkms/kernel_ppp_mppe/0.0.5/build/ppp_mppe.o)
  CC      /var/lib/dkms/kernel_ppp_mppe/0.0.5/build/ppp_generic.mod.o
  LD [M]  /var/lib/dkms/kernel_ppp_mppe/0.0.5/build/ppp_generic.ko
  CC      /var/lib/dkms/kernel_ppp_mppe/0.0.5/build/ppp_mppe.mod.o
  LD [M]  /var/lib/dkms/kernel_ppp_mppe/0.0.5/build/ppp_mppe.ko
make: Leaving directory `/home/mdomsch/bk/modinfo/linux-2.6-modinfo'


So my modules built out-of-tree don't get dependency info from 
/lib/modules/${kernelver}/ as I would have hoped.

Thoughts?

Thanks,
Matt


-- 
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
kbuild-devel mailing list
kbuild-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kbuild-devel

Reply via email to