From: Nicholas Piggin <npiggin@gmail.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Simek <monstr@monstr.eu>
Subject: Re: undefined reference to `_GLOBAL_OFFSET_TABLE_'
Date: Sun, 23 Jul 2017 15:15:29 +1000 [thread overview]
Message-ID: <20170723151529.0e38b82c@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <201707230829.N9cu6t7S%fengguang.wu@intel.com>
On Sun, 23 Jul 2017 08:20:30 +0800
kbuild test robot <fengguang.wu@intel.com> wrote:
> Hi Nicholas,
>
> FYI, the error/warning still remains.
FYI, I still suspect it is this bug
https://sourceware.org/bugzilla/show_bug.cgi?id=21017
If so, then I'm not sure if it can be worked around in Linux.
Thanks,
Nick
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 4b162c530d9c101381500e586fedb1340595a6ff
> commit: 799c43415442414b1032580c47684cb709dfed6d kbuild: thin archives make default for all archs
> date: 3 weeks ago
> config: microblaze-allnoconfig (attached as .config)
> compiler: microblaze-linux-gcc (GCC) 6.2.0
> reproduce:
> wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 799c43415442414b1032580c47684cb709dfed6d
> # save the attached .config to linux build tree
> make.cross ARCH=microblaze
>
> All errors (new ones prefixed by >>):
>
> mm/slub.o: In function `__slab_free.isra.13':
> >> (.text+0x1038): undefined reference to `_GLOBAL_OFFSET_TABLE_'
> scripts/link-vmlinux.sh: line 93: 56533 Segmentation fault ${LD} ${LDFLAGS} ${LDFLAGS_vmlinux} -o ${2} -T ${lds} ${objects}
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2017-07-23 5:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-23 0:20 undefined reference to `_GLOBAL_OFFSET_TABLE_' kbuild test robot
2017-07-23 5:15 ` Nicholas Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-29 23:30 kbuild test robot
2017-08-06 9:47 kbuild test robot
2017-08-13 1:35 kbuild test robot
2017-08-20 0:37 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
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=20170723151529.0e38b82c@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.