From: kbuild test robot <lkp@intel.com>
To: Rob Herring <robh@kernel.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: make[2]: *** No rule to make target 'arch/sh/boot/dts/.dtb.S', needed by 'arch/sh/boot/dts/.dtb.o'.
Date: Fri, 30 Nov 2018 16:02:05 +0800 [thread overview]
Message-ID: <201811301603.beWc8kwV%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
Hi Rob,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 94f371cb73944b410a269d570d6946c042f2ddd0
commit: 37c8a5fafa3bb7dcdd51774be353be6cb2912b86 kbuild: consolidate Devicetree dtb build rules
date: 8 weeks ago
config: sh-j2_defconfig (attached as .config)
compiler: sh4-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 37c8a5fafa3bb7dcdd51774be353be6cb2912b86
# save the attached .config to linux build tree
GCC_VERSION=7.2.0 make.cross ARCH=sh
All errors (new ones prefixed by >>):
>> make[2]: *** No rule to make target 'arch/sh/boot/dts/.dtb.S', needed by 'arch/sh/boot/dts/.dtb.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/gzip, Size: 11995 bytes --]
next reply other threads:[~2018-11-30 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 8:02 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-20 6:50 kbuild test robot
2018-11-12 20:29 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=201811301603.beWc8kwV%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®