From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
kbuild-all@01.org, linux-kernel@vger.kernel.org,
Michal Marek <mmarek@suse.cz>
Subject: Re: Makefile:610: arch/m32r/Makefile: No such file or directory
Date: Mon, 28 Dec 2015 17:44:19 +0530 [thread overview]
Message-ID: <20151228121419.GA23624@sudip-pc> (raw)
In-Reply-To: <201512281648.h80lcrRG%fengguang.wu@intel.com>
On Mon, Dec 28, 2015 at 04:17:51PM +0800, kbuild test robot wrote:
> 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
Hi Fengguang,
I tried to reproduce this but the only error that I am getting is:
gcc-4.9.0-nolibc/m32r-linux/bin/m32r-linux-ld: target elf32-m32r not found
make[3]: *** [arch/m32r/boot/compressed/piggy.o] Error 1
make[2]: *** [arch/m32r/boot/compressed/vmlinux] Error 2
make[1]: *** [zImage] Error 2
make[1]: *** Waiting for unfinished jobs....
ERROR: "memory_start" [fs/udf/udf.ko] undefined!
ERROR: "memory_end" [fs/udf/udf.ko] undefined!
ERROR: "memory_end" [drivers/scsi/sg.ko] undefined!
ERROR: "memory_start" [drivers/scsi/sg.ko] undefined!
ERROR: "memory_end" [drivers/i2c/i2c-dev.ko] undefined!
ERROR: "memory_start" [drivers/i2c/i2c-dev.ko] undefined!
make[2]: *** [__modpost] Error 1
make[1]: *** [modules] Error 2
regards
sudip
next prev parent reply other threads:[~2015-12-28 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 8:17 Makefile:610: arch/m32r/Makefile: No such file or directory kbuild test robot
2015-12-28 12:14 ` Sudip Mukherjee [this message]
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=20151228121419.GA23624@sudip-pc \
--to=sudipm.mukherjee@gmail.com \
--cc=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