From: kbuild test robot <fengguang.wu@intel.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Michal Marek <mmarek@suse.cz>
Subject: Makefile:610: arch/m32r/Makefile: No such file or directory
Date: Mon, 28 Dec 2015 16:17:51 +0800 [thread overview]
Message-ID: <201512281648.h80lcrRG%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2749 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 74bf8efb5fa6e958d2d7c7917b8bb672085ec0c6
commit: a436bb7b806383ae0593cab53d17fc9676270cd3 kbuild: use relative path more to include Makefile
date: 9 months ago
config: m32r-m32104ut_defconfig (attached as .config)
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 a436bb7b806383ae0593cab53d17fc9676270cd3
# save the attached .config to linux build tree
make.cross ARCH=m32r
All errors (new ones prefixed by >>):
Makefile:350: scripts/Kbuild.include: No such file or directory
>> Makefile:610: arch/m32r/Makefile: No such file or directory
Makefile:782: scripts/Makefile.kasan: No such file or directory
Makefile:783: scripts/Makefile.extrawarn: No such file or directory
make[1]: *** No rule to make target 'scripts/Makefile.extrawarn'.
make[1]: *** No rule to make target 'scripts/Makefile.kasan'.
>> make[1]: *** No rule to make target 'arch/m32r/Makefile'.
make[1]: Failed to remake makefile 'scripts/Makefile.extrawarn'.
make[1]: Failed to remake makefile 'scripts/Makefile.kasan'.
make[1]: Failed to remake makefile 'arch/m32r/Makefile'.
make: *** empty variable name. Stop.
make[1]: *** [scripts_basic] Error 2
scripts/Makefile.asm-generic:11: scripts/Kbuild.include: No such file or directory
make[2]: *** No rule to make target 'scripts/Kbuild.include'.
make[2]: Failed to remake makefile 'scripts/Kbuild.include'.
make[1]: *** [asm-generic] Error 2
make[1]: Target 'headers_install' not remade because of errors.
make: *** [sub-make] Error 2
vim +610 Makefile
594 echo >&2 ; \
595 /bin/false)
596
597 endif # KBUILD_EXTMOD
598
599 else
600 # Dummy target needed, because used as prerequisite
601 include/config/auto.conf: ;
602 endif # $(dot-config)
603
604 # The all: target is the default when no target is given on the
605 # command line.
606 # This allow a user to issue only 'make' to build a kernel including modules
607 # Defaults to vmlinux, but the arch makefile usually adds further targets
608 all: vmlinux
609
> 610 include arch/$(SRCARCH)/Makefile
611
612 KBUILD_CFLAGS += $(call cc-option,-fno-delete-null-pointer-checks,)
613
614 ifdef CONFIG_CC_OPTIMIZE_FOR_SIZE
615 KBUILD_CFLAGS += -Os $(call cc-disable-warning,maybe-uninitialized,)
616 else
617 KBUILD_CFLAGS += -O2
618 endif
---
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: 9757 bytes --]
next reply other threads:[~2015-12-28 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 8:17 kbuild test robot [this message]
2015-12-28 12:14 ` Sudip Mukherjee
2015-12-29 3:50 ` Fengguang Wu
2015-12-30 6:42 ` Sudip Mukherjee
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=201512281648.h80lcrRG%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=yamada.masahiro@socionext.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®