linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	Michal Simek <monstr@monstr.eu>
Subject: Re: net/sunrpc/stats.c:204: undefined reference to `_GLOBAL_OFFSET_TABLE_'
Date: Tue, 4 Oct 2016 12:33:31 +0800	[thread overview]
Message-ID: <20161004043331.lg5fi3udnikxmoq7@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1609231706250.9311@knanqh.ubzr>

CC Michal. It looks like a microblaze specific error. I'll blacklist
this old error on microblaze if there are no good solutions.

Sorry for the noise!

On Fri, Sep 23, 2016 at 05:11:32PM -0400, Nicolas Pitre wrote:
>On Thu, 22 Sep 2016, kbuild test robot wrote:
>
>> Hi Nicolas,
>>
>> FYI, the error/warning still remains.
>>
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head:   7d1e042314619115153a0f6f06e4552c09a50e13
>> commit: 461a5e51060c93f5844113f4be9dba513cc92830 do_div(): generic optimization for constant divisor on 32-bit machines
>> date:   10 months ago
>> config: microblaze-mmu_defconfig (attached as .config)
>> compiler: microblaze-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 461a5e51060c93f5844113f4be9dba513cc92830
>>         # save the attached .config to linux build tree
>>         make.cross ARCH=microblaze
>>
>> All errors (new ones prefixed by >>):
>>
>>    net/built-in.o: In function `rpc_print_iostats':
>> >> net/sunrpc/stats.c:204: undefined reference to `_GLOBAL_OFFSET_TABLE_'
>>    scripts/link-vmlinux.sh: line 52:  5714 Segmentation fault      ${LD} ${LDFLAGS} ${LDFLAGS_vmlinux} -o ${2} -T ${lds} ${KBUILD_VMLINUX_INIT} --start-group ${KBUILD_VMLINUX_MAIN} --end-group ${1}
>
>The problem must be at your end, especially if the toolchain exhibits
>segmentation faults.
>
>Following exactly the instructions above, I get:
>
>[...]
>  LD      vmlinux
>  SORTEX  vmlinux
>  SYSMAP  System.map
>  OBJCOPY arch/microblaze/boot/linux.bin
>  Building modules, stage 2.
>  MODPOST 3 modules
>  CC      crypto/drbg.mod.o
>  CC      crypto/echainiv.mod.o
>  CC      crypto/jitterentropy_rng.mod.o
>  LD [M]  crypto/jitterentropy_rng.ko
>  LD [M]  crypto/drbg.ko
>  LD [M]  crypto/echainiv.ko
>Kernel: arch/microblaze/boot/linux.bin is ready  (#1)
>
>
>Nicolas

  reply	other threads:[~2016-10-04  4:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22  3:52 net/sunrpc/stats.c:204: undefined reference to `_GLOBAL_OFFSET_TABLE_' kbuild test robot
2016-09-23 21:11 ` Nicolas Pitre
2016-10-04  4:33   ` Fengguang Wu [this message]
2016-10-04 13:08     ` Nicolas Pitre
2016-10-05 23:57       ` Fengguang Wu
2016-10-06  2:43         ` Nicolas Pitre
2016-10-06 11:27           ` Fengguang Wu
  -- strict thread matches above, loose matches on Subject: below --
2016-10-01 23:44 kbuild test robot
2016-10-04  4:06 ` Nicolas Pitre
2016-09-16 11:57 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=20161004043331.lg5fi3udnikxmoq7@wfg-t540p.sh.intel.com \
    --to=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=monstr@monstr.eu \
    --cc=nicolas.pitre@linaro.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).