From: Nicholas Piggin <npiggin@gmail.com>
To: Michal Simek <monstr@monstr.eu>
Cc: kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, linux-kernel@vger.kernel.org,
Masahiro Yamada <yamada.masahiro@socionext.com>
Subject: Re: undefined reference to `_GLOBAL_OFFSET_TABLE_'
Date: Tue, 22 Aug 2017 22:14:43 +1000 [thread overview]
Message-ID: <20170822221443.006a2121@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <8e27843f-cb87-4e2e-32f1-1e1cd45cb4ee@monstr.eu>
On Tue, 22 Aug 2017 11:19:02 +0200
Michal Simek <monstr@monstr.eu> wrote:
> On 20.8.2017 05:36, Nicholas Piggin wrote:
> > On Sun, 20 Aug 2017 08:37:36 +0800
> > kbuild test robot <fengguang.wu@intel.com> wrote:
> >
> >> Hi Nicholas,
> >>
> >> FYI, the error/warning still remains.
> >
> > Still same answer as before, i.e., it seems to be this toolchain bug:
> >
> > https://sourceware.org/bugzilla/show_bug.cgi?id=21017
> >
> > I've had no response from the microblaze maintainer, so please stop
> > generating this warning now. If we get a bug report from a user who
> > actually cares and will test toolchain fixes then we can easily work
> > with them.
> >
> > Many thanks for the very good service this build system provides!
>
> Can you please point me to the log?
Hmm, don't know if they keep a full log, but the error is
mm/slub.o: In function `__slab_free.isra.13':
>> (.text+0x1038): undefined reference to `_GLOBAL_OFFSET_TABLE_'
scripts/link-vmlinux.sh: line 93: 48917 Segmentation fault ${LD} ${LDFLAGS} ${LDFLAGS_vmlinux} -o ${2} -T ${lds} ${objects}
I suspect the change to thin archives, allowed the linker more
flexibility to satisfy all relocations with GOT relative. And
that would cause the bug.
If you could verify that the upstream kernel build succeeds with
an upstream binutils using allnoconfig, then we could see about
updating the kbuild test robot's toolchain.
Thanks,
Nick
next prev parent reply other threads:[~2017-08-22 12:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 0:37 undefined reference to `_GLOBAL_OFFSET_TABLE_' kbuild test robot
2017-08-20 3:36 ` Nicholas Piggin
2017-08-22 1:59 ` Fengguang Wu
2017-08-22 9:19 ` Michal Simek
2017-08-22 12:14 ` Nicholas Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-13 1:35 kbuild test robot
2017-08-06 9:47 kbuild test robot
2017-07-29 23:30 kbuild test robot
2017-07-23 0:20 kbuild test robot
2017-07-23 5:15 ` Nicholas Piggin
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=20170822221443.006a2121@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=monstr@monstr.eu \
--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