>> 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 as the driver is not an upstream one. But this issue happens randomly, not 100% reproducible. And it happens on different driver sometimes. So I don't think it would be driver related and pointing out the driver name would not help much anyway. What I'm trying to understand is under what condition fixdep is triggered in the kernel build process. Is the .d file always generated for every driver? If that file is always created, could it be a timing issue that the .d file was actually created but then deleted when fixdep trying to find it? Thank you Sam! I'm not familiar with kernel build scripts, any idea is really appreciated. -Fei -- 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
