From patchwork Mon Aug 26 19:22:46 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Yang, Fei" X-Patchwork-Id: 2849751 Return-Path: X-Original-To: patchwork-linux-kbuild@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork2.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.19.201]) by patchwork2.web.kernel.org (Postfix) with ESMTP id EE3F6BF546 for ; Mon, 26 Aug 2013 19:22:59 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id E882320320 for ; Mon, 26 Aug 2013 19:22:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E7E15201DD for ; Mon, 26 Aug 2013 19:22:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752141Ab3HZTW5 (ORCPT ); Mon, 26 Aug 2013 15:22:57 -0400 Received: from mga14.intel.com ([143.182.124.37]:57551 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752103Ab3HZTW4 convert rfc822-to-8bit (ORCPT ); Mon, 26 Aug 2013 15:22:56 -0400 Received: from azsmga001.ch.intel.com ([10.2.17.19]) by azsmga102.ch.intel.com with ESMTP; 26 Aug 2013 12:22:56 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.89,961,1367996400"; d="scan'208,223";a="351857696" Received: from orsmsx106.amr.corp.intel.com ([10.22.225.133]) by azsmga001.ch.intel.com with ESMTP; 26 Aug 2013 12:22:47 -0700 Received: from orsmsx156.amr.corp.intel.com (10.22.240.22) by ORSMSX106.amr.corp.intel.com (10.22.225.133) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 26 Aug 2013 12:22:47 -0700 Received: from orsmsx102.amr.corp.intel.com ([169.254.1.106]) by ORSMSX156.amr.corp.intel.com ([169.254.8.154]) with mapi id 14.03.0123.003; Mon, 26 Aug 2013 12:22:46 -0700 From: "Yang, Fei" To: "linux-kbuild@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 Thread-Topic: Can anyone suggest a better fix? Not sure if I understand the problem, but the patch fixed it Thread-Index: Ac6ikZoVxBxE4fuwQdCkVcy9DopOgA== Date: Mon, 26 Aug 2013 19:22:46 +0000 Message-ID: <02E7334B1630744CBDC55DA85862258348E431C1@ORSMSX102.amr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.140] MIME-Version: 1.0 Sender: linux-kbuild-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kbuild@vger.kernel.org X-Spam-Status: No, score=-9.3 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_HI, RP_MATCHES_RCVD, UNPARSEABLE_RELAY autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP From 5e6501efa26bc19dad0b43e3a2b0daa81408a8ae Mon Sep 17 00:00:00 2001 From: Fei Yang 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 --- 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: ");