From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [zen-kernel-zen-kernel:5.7/muqss-rebase 22/23] ld.lld: error: undefined symbol: sysctl_sched_rt_runtime
Date: Sat, 27 Jun 2020 00:58:12 +0800 [thread overview]
Message-ID: <202006270010.5PFlA6Hu%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1659 bytes --]
TO: Steven Barrett <steven@liquorix.net>
tree: https://github.com/zen-kernel/zen-kernel 5.7/muqss-rebase
head: fe08666c5308d1f6d9e2c863ceae90cb276ccb05
commit: 668242641cd913ec5b1dc450880c5d2db3be27c6 [22/23] muqss: Update to MuQSS v202
config: x86_64-allyesconfig (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 6e11ed52057ffc39941cb2de6d93cae522db4782)
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 668242641cd913ec5b1dc450880c5d2db3be27c6
# 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: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: sysctl_sched_rt_runtime
>>> referenced by rcutorture.c
>>> rcu/rcutorture.o:(rcutorture_booster_init) in archive kernel/built-in.a
>>> referenced by rcutorture.c
>>> rcu/rcutorture.o:(rcutorture_booster_init) in archive kernel/built-in.a
>>> referenced by rcutorture.c
>>> rcu/rcutorture.o:(rcutorture_booster_init) in archive kernel/built-in.a
>>> referenced 2 more times
---
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: 74030 bytes --]
reply other threads:[~2020-06-26 16:58 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=202006270010.5PFlA6Hu%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.