On 27.8.2013 21:05, Yang, Fei wrote: >>> From: Fei Yang <fei.yang@xxxxxxxxx> >>> Date: Mon, 26 Aug 2013 11:21:48 -0700 >>> Subject: [PATCH] FIXDEP: error opening depfile >>> >>> Met a kernel build issue where fixdep fails to open a depfile, >>> fixdep: error opening depfile: drivers/driver-name/.driver-code.o.d: >>> No such file or directory >>> make[4]: *** [drivers/driver-name/driver-code.o] Error 2 >>> make[3]: *** [drivers/driver-name] Error 2 Don't know why the expected >>> file was not created, but the assumption that the file had been >>> created might not be true, so simply return for such failure. > >> I tried to grep: >> git grep "driver-name" >> >> No hits. >> >> Are you trying to fix a build issue with something out-of-tree - or is this only in linux-next? > > Oh, I changed the driver and file name in the error message to avoid > unnecessary confusion You achieved quite the opposite :-). > as the driver is not an upstream one. But this issue happens randomly, not 100% > reproducible. And it happens on different driver sometimes. Are you able to reproduce this with the vanilla kernel? If so, details please. If not, then this can be something with your module's build system. Are you using anything fancier than $ cat Makefile obj-m += my-module.o $ make -C <kernel build tree> M=$PWD ? Michal -- 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
