From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [dax:xarray-pagecache 67/67] ld.lld: error: undefined symbol: dump_iomap_page
Date: Fri, 29 May 2020 13:22:21 +0800 [thread overview]
Message-ID: <202005291319.sYFGipKN%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]
TO: "Matthew, Wilcox, (Oracle)," <willy@infradead.org>
tree: git://git.infradead.org/users/willy/linux-dax.git xarray-pagecache
head: 85277e3f0e1527f5f40225fa49a5cb2441b2b548
commit: 85277e3f0e1527f5f40225fa49a5cb2441b2b548 [67/67] debug
config: x86_64-allnoconfig (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 2d068e534f1671459e1b135852c1b3c10502e929)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
git checkout 85277e3f0e1527f5f40225fa49a5cb2441b2b548
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
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 <<):
>> ld.lld: error: undefined symbol: dump_iomap_page
>>> referenced by filemap.c
>>> filemap.o:(wait_on_page_bit_common) in archive mm/built-in.a
---
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: 7413 bytes --]
reply other threads:[~2020-05-29 5:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202005291319.sYFGipKN%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.