From: kbuild test robot <fengguang.wu@intel.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Jesper Nilsson <jespern@axis.com>
Subject: cris-linux-objcopy: error: the input file 'arch/cris/boot/rescue/rescue.o' has no sections
Date: Sun, 30 Oct 2016 10:53:36 +0800 [thread overview]
Message-ID: <201610301031.645EEvxz%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]
Hi Guenter,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: a909d3e636995ba7c349e2ca5dbb528154d4ac30
commit: f9f3f864b5e8c09d7837d8980edba4ad52969819 cris: Fix section mismatches in architecture startup code
date: 11 months ago
config: cris-allnoconfig (attached as .config)
compiler: cris-linux-gcc (GCC) 6.2.0
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 f9f3f864b5e8c09d7837d8980edba4ad52969819
# save the attached .config to linux build tree
make.cross ARCH=cris
All errors (new ones prefixed by >>):
>> cris-linux-objcopy: error: the input file 'arch/cris/boot/rescue/rescue.o' has no sections
---
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: 4351 bytes --]
next reply other threads:[~2016-10-30 2:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 2:53 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-16 4:39 kbuild test robot
2016-10-01 23:18 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=201610301031.645EEvxz%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=jespern@axis.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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®