From: kbuild test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kbuild-all@01.org, Michal Marek <mmarek@suse.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 2/3] Kbuild: don't add obj tree in additional includes
Date: Tue, 14 Jun 2016 05:38:08 +0800 [thread overview]
Message-ID: <201606140559.v8LZdIWP%fengguang.wu@intel.com> (raw)
In-Reply-To: <1465852786-3559357-2-git-send-email-arnd@arndb.de>
[-- Attachment #1: Type: text/plain, Size: 2190 bytes --]
Hi,
[auto build test ERROR on kbuild/for-next]
[also build test ERROR on v4.7-rc3 next-20160609]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Arnd-Bergmann/Kbuild-don-t-add-to-include-path/20160614-052242
base: https://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild.git for-next
config: i386-tinyconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> arch/x86/realmode/rm/realmode.lds.S:75:20: fatal error: pasyms.h: No such file or directory
#include "pasyms.h"
^
compilation terminated.
vim +75 arch/x86/realmode/rm/realmode.lds.S
b3266bd6 Jarkko Sakkinen 2012-05-08 59 .bss : {
b3266bd6 Jarkko Sakkinen 2012-05-08 60 *(.bss*)
b3266bd6 Jarkko Sakkinen 2012-05-08 61 }
b3266bd6 Jarkko Sakkinen 2012-05-08 62
b3266bd6 Jarkko Sakkinen 2012-05-08 63 /* End signature for integrity checking */
b3266bd6 Jarkko Sakkinen 2012-05-08 64 . = ALIGN(4);
b3266bd6 Jarkko Sakkinen 2012-05-08 65 .signature : {
b3266bd6 Jarkko Sakkinen 2012-05-08 66 *(.signature)
b3266bd6 Jarkko Sakkinen 2012-05-08 67 }
b3266bd6 Jarkko Sakkinen 2012-05-08 68
b3266bd6 Jarkko Sakkinen 2012-05-08 69 /DISCARD/ : {
b3266bd6 Jarkko Sakkinen 2012-05-08 70 *(.note*)
b3266bd6 Jarkko Sakkinen 2012-05-08 71 *(.debug*)
b3266bd6 Jarkko Sakkinen 2012-05-08 72 *(.eh_frame*)
b3266bd6 Jarkko Sakkinen 2012-05-08 73 }
b3266bd6 Jarkko Sakkinen 2012-05-08 74
b3266bd6 Jarkko Sakkinen 2012-05-08 @75 #include "pasyms.h"
b3266bd6 Jarkko Sakkinen 2012-05-08 76 }
:::::: The code at line 75 was first introduced by commit
:::::: b3266bd6ff52efb9e57c7fbfff4c8f7363dfaab3 x86, realmode: realmode.bin infrastructure
:::::: TO: Jarkko Sakkinen <jarkko.sakkinen@intel.com>
:::::: CC: H. Peter Anvin <hpa@linux.intel.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 6345 bytes --]
next prev parent reply other threads:[~2016-06-13 21:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 21:19 [PATCH 1/3] Kbuild: don't add ../../ to include path Arnd Bergmann
2016-06-13 21:19 ` [PATCH 2/3] Kbuild: don't add obj tree in additional includes Arnd Bergmann
2016-06-13 21:38 ` kbuild test robot [this message]
2016-06-13 22:42 ` kbuild test robot
2016-06-15 15:42 ` Arnd Bergmann
2016-06-13 22:51 ` kbuild test robot
2016-06-13 21:19 ` [PATCH 3/3] Kbuild: avoid duplicate include path Arnd Bergmann
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=201606140559.v8LZdIWP%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=kbuild-all@01.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
/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
all inboxes | Powered by JetHome®