From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [zen-kernel-zen-kernel:5.12/futex2 13/16] fork.c:(.text.mm_release+0x74): undefined reference to `ksys_futex_wake'
Date: Wed, 16 Jun 2021 04:42:33 +0800 [thread overview]
Message-ID: <202106160429.LsfN058W-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]
Hi André,
FYI, the error/warning still remains.
tree: https://github.com/zen-kernel/zen-kernel 5.12/futex2
head: 81255c11c48cc2302883425c87318f9cad37e7e6
commit: 74b2323f995135be08649b48df710e78efcf7f62 [13/16] kernel: Enable waitpid() for futex2
config: mips-randconfig-r025-20210615 (attached as .config)
compiler: mipsel-linux-gcc (GCC) 9.3.0
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
# https://github.com/zen-kernel/zen-kernel/commit/74b2323f995135be08649b48df710e78efcf7f62
git remote add zen-kernel-zen-kernel https://github.com/zen-kernel/zen-kernel
git fetch --no-tags zen-kernel-zen-kernel 5.12/futex2
git checkout 74b2323f995135be08649b48df710e78efcf7f62
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips
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 >>):
mipsel-linux-ld: kernel/fork.o: in function `mm_release':
>> fork.c:(.text.mm_release+0x74): undefined reference to `ksys_futex_wake'
---
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: 26181 bytes --]
reply other threads:[~2021-06-15 20:42 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=202106160429.LsfN058W-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.