On Thu, Jan 14, 2016 at 10:50:12AM +0800, kbuild test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git asm-exports > head: 5719a6be97e89c65e2b432b45850100c96c7419a > commit: 5719a6be97e89c65e2b432b45850100c96c7419a [6/6] arm: move exports to definitions > config: arm-viper_defconfig (attached as .config) > reproduce: > wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross > chmod +x ~/bin/make.cross > git checkout 5719a6be97e89c65e2b432b45850100c96c7419a > # save the attached .config to linux build tree > make.cross ARCH=arm > > All errors (new ones prefixed by >>): > > >> ERROR: "__raw_readsb" [drivers/ata/pata_pcmcia.ko] undefined! > >> ERROR: "__raw_writesb" [drivers/ata/pata_pcmcia.ko] undefined! Arrgh... OK, I see what's going on - export in a lib-y object. For lib/*.c we deal with that by putting such objects into obj-y; the same certainly can be done for *.S, but I wonder if a better solution would be to have lib-y objects scanned for __ksymtab_strings section (grepping in objdump -h output) and treat the ones that have such as obj-y. Comments? -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
