From: kbuild test robot <fengguang.wu@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Stafford Horne <shorne@gmail.com>
Subject: undefined reference to `_text'
Date: Sun, 1 Jan 2017 11:11:57 +0800 [thread overview]
Message-ID: <201701011154.VDodmoBw%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
Hi Randy,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 238d1d0f79f619d75c2cc741d6770fb0986aef24
commit: 7c7808ce107d63e158dbbc3af085980985a0c3c4 openrisc: prevent VGA console, fix builds
date: 3 weeks ago
config: openrisc-alldefconfig (attached as .config)
compiler: or32-linux-gcc (GCC) 4.5.1-or32-1.0rc1
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 7c7808ce107d63e158dbbc3af085980985a0c3c4
# save the attached .config to linux build tree
make.cross ARCH=openrisc
All errors (new ones prefixed by >>):
.tmp_kallsyms1.o: In function `kallsyms_relative_base':
>> (.rodata+0x8a18): undefined reference to `_text'
---
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: 6061 bytes --]
next reply other threads:[~2017-01-01 3:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 3:11 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-25 7:21 undefined reference to `_text' kbuild test robot
2016-12-25 8:36 ` Stafford Horne
2016-12-13 21:00 kbuild test robot
2016-12-14 1:31 ` Stafford Horne
2016-12-14 12:58 ` Stafford Horne
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=201701011154.VDodmoBw%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=shorne@gmail.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;
as well as URLs for NNTP newsgroup(s).