From: "Yang, Fei" <fei.yang@intel.com>
To: "linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
"'linux-kernel@vger.kernel.org' (linux-kernel@vger.kernel.org)"
<linux-kernel@vger.kernel.org>
Subject: Can anyone suggest a better fix? Not sure if I understand the problem, but the patch fixed it
Date: Mon, 26 Aug 2013 19:22:46 +0000 [thread overview]
Message-ID: <02E7334B1630744CBDC55DA85862258348E431C1@ORSMSX102.amr.corp.intel.com> (raw)
>From 5e6501efa26bc19dad0b43e3a2b0daa81408a8ae Mon Sep 17 00:00:00 2001
From: Fei Yang <fei.yang@intel.com>
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.
Change-Id: I299c01f2e3f6e1d04b19ced34ebeb964e16494e6
Signed-off-by: Fei Yang <fei.yang@intel.com>
---
scripts/basic/fixdep.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/basic/fixdep.c b/scripts/basic/fixdep.c
index cb1f50c..2c065e5 100644
--- a/scripts/basic/fixdep.c
+++ b/scripts/basic/fixdep.c
@@ -377,7 +377,7 @@ static void print_deps(void)
if (fd < 0) {
fprintf(stderr, "fixdep: error opening depfile: ");
perror(depfile);
- exit(2);
+ return;
}
if (fstat(fd, &st) < 0) {
fprintf(stderr, "fixdep: error fstat'ing depfile: ");
--
1.7.9.5
next reply other threads:[~2013-08-26 19:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 19:22 Yang, Fei [this message]
2013-08-26 20:10 ` Can anyone suggest a better fix? Not sure if I understand the problem, but the patch fixed it Sam Ravnborg
2013-08-27 19:05 ` Yang, Fei
2013-08-28 15:07 ` Michal Marek
2013-08-28 15:08 ` Michal Marek
2013-08-28 16:27 ` Yang, Fei
2013-08-28 16:31 ` Michal Marek
2013-08-28 16:47 ` Yang, Fei
2013-08-29 17:55 ` Sam Ravnborg
2013-08-30 15:10 ` Michal Marek
2013-08-29 17:55 ` Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=02E7334B1630744CBDC55DA85862258348E431C1@ORSMSX102.amr.corp.intel.com \
--to=fei.yang@intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).