From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [linux-nvme:nvme-5.8 26/33] io-cmd-bdev.c:undefined reference to `t10_pi_type1_crc'
Date: Fri, 22 May 2020 03:03:09 +0800 [thread overview]
Message-ID: <202005220306.P96iFPve%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2207 bytes --]
tree: git://git.infradead.org/nvme.git nvme-5.8
head: 08b17299f88361a4ad49bf1c7ff9338bbe99ce85
commit: 79250d19e14f25bbd23a5cb0b4c309c4c994d93e [26/33] nvmet: add metadata characteristics for a namespace
config: arm64-randconfig-r005-20200520 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 3393cc4cebf9969db94dc424b7a2b6195589c33b)
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install arm64 cross compiling tool for clang build
# apt-get install binutils-aarch64-linux-gnu
git checkout 79250d19e14f25bbd23a5cb0b4c309c4c994d93e
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
aarch64-linux-gnu-ld: drivers/nvme/target/io-cmd-bdev.o: in function `nvmet_bdev_ns_enable':
>> io-cmd-bdev.c:(.text+0x16c): undefined reference to `t10_pi_type1_crc'
aarch64-linux-gnu-ld: drivers/nvme/target/io-cmd-bdev.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `t10_pi_type1_crc' which may bind externally can not be used when making a shared object; recompile with -fPIC
io-cmd-bdev.c:(.text+0x16c): dangerous relocation: unsupported relocation
>> aarch64-linux-gnu-ld: io-cmd-bdev.c:(.text+0x170): undefined reference to `t10_pi_type1_crc'
>> aarch64-linux-gnu-ld: io-cmd-bdev.c:(.text+0x17c): undefined reference to `t10_pi_type3_crc'
aarch64-linux-gnu-ld: drivers/nvme/target/io-cmd-bdev.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `t10_pi_type3_crc' which may bind externally can not be used when making a shared object; recompile with -fPIC
io-cmd-bdev.c:(.text+0x17c): dangerous relocation: unsupported relocation
aarch64-linux-gnu-ld: io-cmd-bdev.c:(.text+0x180): undefined reference to `t10_pi_type3_crc'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 47549 bytes --]
next reply other threads:[~2020-05-21 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 19:03 kbuild test robot [this message]
2020-05-21 19:47 ` [linux-nvme:nvme-5.8 26/33] io-cmd-bdev.c:undefined reference to `t10_pi_type1_crc' Christoph Hellwig
2020-05-21 19:55 ` Martin K. Petersen
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=202005220306.P96iFPve%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.