From: kbuild test robot <fengguang.wu@intel.com>
To: Rich Felker <dalias@libc.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: make[2]: *** No rule to make target 'arch/sh/boot/dts/.dtb.o', needed by 'arch/sh/boot/dts/built-in.o'.
Date: Sun, 11 Sep 2016 13:13:15 +0800 [thread overview]
Message-ID: <201609111313.H8SsAxyL%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
Hi Rich,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 98ac9a608dc79ba8a20cee77fe959a6dfccdaa63
commit: 190fe191cfbead9fe089453dd092869c9469c6d4 sh: add support for linking a builtin device tree blob in the kernel
date: 6 weeks ago
config: sh-allmodconfig (attached as .config)
compiler: sh4-linux-gnu-gcc (Debian 5.4.0-6) 5.4.0 20160609
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 190fe191cfbead9fe089453dd092869c9469c6d4
# save the attached .config to linux build tree
make.cross ARCH=sh
All errors (new ones prefixed by >>):
>> make[2]: *** No rule to make target 'arch/sh/boot/dts/.dtb.o', needed by 'arch/sh/boot/dts/built-in.o'.
make[2]: Target '__build' not remade because of errors.
---
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: 40537 bytes --]
next reply other threads:[~2016-09-11 5:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 5:13 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-22 5:45 make[2]: *** No rule to make target 'arch/sh/boot/dts/.dtb.o', needed by 'arch/sh/boot/dts/built-in.o' kbuild test robot
2017-01-15 6:41 kbuild test robot
2016-12-11 2:08 kbuild test robot
2016-12-04 8:19 kbuild test robot
2016-11-06 6:10 kbuild test robot
2016-09-04 18:12 kbuild test robot
2016-08-22 11:45 kbuild test robot
2016-08-07 2:00 kbuild test robot
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=201609111313.H8SsAxyL%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=dalias@libc.org \
--cc=kbuild-all@01.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).