Hi Christoph, 2018-07-28 16:23 GMT+09:00 kbuild test robot <lkp@xxxxxxxxx>: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git kconfig2 > head: 0e83fd903bc85173711186755591b61405647cf3 > commit: 2cc1bfaf2c45056c73970a99c3a7467e157f56aa [1/10] um: stop abusing KBUILD_KCONFIG > config: um-x86_64_defconfig > compiler: gcc-7 (Debian 7.3.0-16) 7.3.0 > reproduce: > git checkout 2cc1bfaf2c45056c73970a99c3a7467e157f56aa > make ARCH=um SUBARCH=x86_64 defconfig > make ARCH=um SUBARCH=x86_64 Hmm. SUBARCH is used by arch/x86/um/Kconfig to choose 64BIT. Maybe, do we need $(SUBSRCARCH) ? (In hindsight, HOST_ARCH and HOST_SRCARCH might be clearer, though...) > All errors (new ones prefixed by >>): > >>> arch/um/Kconfig:3: can't open file "arch/x86_64/um/Kconfig" > make[2]: *** [defconfig] Error 1 > make[1]: *** [defconfig] Error 2 > make: *** [sub-make] Error 2 > -- >>> arch/um/Kconfig:3: can't open file "arch/x86_64/um/Kconfig" > make[2]: *** [oldconfig] Error 1 > make[1]: *** [oldconfig] Error 2 > make: *** [sub-make] Error 2 > -- >>> arch/um/Kconfig:3: can't open file "arch/x86_64/um/Kconfig" > make[2]: *** [olddefconfig] Error 1 > make[1]: *** [olddefconfig] Error 2 > make: *** [sub-make] Error 2 > > vim +3 arch/um/Kconfig > > 2 > > 3 source "arch/$(SUBARCH)/um/Kconfig" > > --- > 0-DAY kernel test infrastructure Open Source Technology Center > https://lists.01.org/pipermail/kbuild-all Intel Corporation > -- > 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 -- Best Regards Masahiro Yamada -- 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
