From: Stafford Horne <shorne@gmail.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: undefined reference to `_text'
Date: Wed, 14 Dec 2016 21:58:11 +0900 [thread overview]
Message-ID: <20161214125811.GE2650@lianli.shorne-pla.net> (raw)
In-Reply-To: <201612140506.lku9rvix%fengguang.wu@intel.com>
On Wed, Dec 14, 2016 at 05:00:22AM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: b78b499a67c3f77aeb6cd0b54724bc38b141255d
> commit: 7c7808ce107d63e158dbbc3af085980985a0c3c4 openrisc: prevent VGA console, fix builds
> date: 31 hours 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'
>
I just sent a patch for this.
"openrisc: Add _text symbol to fix ksym build error"
-Stafford
next prev parent reply other threads:[~2016-12-14 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 21:00 undefined reference to `_text' kbuild test robot
2016-12-14 1:31 ` Stafford Horne
2016-12-14 12:58 ` Stafford Horne [this message]
2016-12-25 7:21 kbuild test robot
2016-12-25 8:36 ` Stafford Horne
2017-01-01 3:11 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=20161214125811.GE2650@lianli.shorne-pla.net \
--to=shorne@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).