linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 5363/11953] /kbuild/worktree/build-ktools-consumer/tools/virtio/./linux/spinlock.h:16: undefined reference to `pthread_spin_lock'
Date: Sat, 12 Mar 2022 12:50:51 +0800	[thread overview]
Message-ID: <202203121220.3s8QdG0u-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   71941773e143369a73c9c4a3b62fbb60736a1182
commit: 5a27a43efd1d5cd55dd5988cac596bdea7294d73 [5363/11953] gfs2: Make use of list_is_first
config: x86_64-rhel-8.3-kselftests (https://download.01.org/0day-ci/archive/20220312/202203121220.3s8QdG0u-lkp@intel.com/config)
compiler: gcc-9 (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0
reproduce (this is a W=1 build):
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=5a27a43efd1d5cd55dd5988cac596bdea7294d73
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout 5a27a43efd1d5cd55dd5988cac596bdea7294d73
        # save the config file to linux build tree
        make W=1 ARCH=x86_64 SHELL=/bin/bash tools/all

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 >>):

   /usr/bin/ld: virtio_ring.o: in function `spin_lock':
>> /kbuild/worktree/build-ktools-consumer/tools/virtio/./linux/spinlock.h:16: undefined reference to `pthread_spin_lock'
   /usr/bin/ld: virtio_ring.o: in function `spin_unlock':
>> /kbuild/worktree/build-ktools-consumer/tools/virtio/./linux/spinlock.h:22: undefined reference to `pthread_spin_unlock'
   /usr/bin/ld: virtio_ring.o: in function `spin_lock':
>> /kbuild/worktree/build-ktools-consumer/tools/virtio/./linux/spinlock.h:16: undefined reference to `pthread_spin_lock'
   /usr/bin/ld: virtio_ring.o: in function `spin_unlock':
>> /kbuild/worktree/build-ktools-consumer/tools/virtio/./linux/spinlock.h:22: undefined reference to `pthread_spin_unlock'
   /usr/bin/ld: virtio_ring.o: in function `spin_lock':
>> /kbuild/worktree/build-ktools-consumer/tools/virtio/./linux/spinlock.h:16: undefined reference to `pthread_spin_lock'
   /usr/bin/ld: virtio_ring.o: in function `spin_unlock':
>> /kbuild/worktree/build-ktools-consumer/tools/virtio/./linux/spinlock.h:22: undefined reference to `pthread_spin_unlock'
   /usr/bin/ld: virtio_ring.o: in function `spin_lock':
>> /kbuild/worktree/build-ktools-consumer/tools/virtio/./linux/spinlock.h:16: undefined reference to `pthread_spin_lock'
   /usr/bin/ld: virtio_ring.o: in function `spin_unlock':
>> /kbuild/worktree/build-ktools-consumer/tools/virtio/./linux/spinlock.h:22: undefined reference to `pthread_spin_unlock'
   /usr/bin/ld: virtio_test.o: in function `spin_lock_init':
   /kbuild/worktree/build-ktools-consumer/tools/virtio/./linux/spinlock.h:10: undefined reference to `pthread_spin_init'
   collect2: error: ld returned 1 exit status
   make[3]: *** [<builtin>: virtio_test] Error 1
   make[3]: *** Waiting for unfinished jobs....
   /usr/bin/ld: virtio_ring.o: in function `spin_lock':
>> /kbuild/worktree/build-ktools-consumer/tools/virtio/./linux/spinlock.h:16: undefined reference to `pthread_spin_lock'
   /usr/bin/ld: virtio_ring.o: in function `spin_unlock':
>> /kbuild/worktree/build-ktools-consumer/tools/virtio/./linux/spinlock.h:22: undefined reference to `pthread_spin_unlock'
   /usr/bin/ld: virtio_ring.o: in function `spin_lock':
>> /kbuild/worktree/build-ktools-consumer/tools/virtio/./linux/spinlock.h:16: undefined reference to `pthread_spin_lock'
   /usr/bin/ld: virtio_ring.o: in function `spin_unlock':
>> /kbuild/worktree/build-ktools-consumer/tools/virtio/./linux/spinlock.h:22: undefined reference to `pthread_spin_unlock'
   /usr/bin/ld: virtio_ring.o: in function `spin_lock':
>> /kbuild/worktree/build-ktools-consumer/tools/virtio/./linux/spinlock.h:16: undefined reference to `pthread_spin_lock'
   /usr/bin/ld: virtio_ring.o: in function `spin_unlock':
>> /kbuild/worktree/build-ktools-consumer/tools/virtio/./linux/spinlock.h:22: undefined reference to `pthread_spin_unlock'
   /usr/bin/ld: virtio_ring.o: in function `spin_lock':
>> /kbuild/worktree/build-ktools-consumer/tools/virtio/./linux/spinlock.h:16: undefined reference to `pthread_spin_lock'
   /usr/bin/ld: virtio_ring.o: in function `spin_unlock':
>> /kbuild/worktree/build-ktools-consumer/tools/virtio/./linux/spinlock.h:22: undefined reference to `pthread_spin_unlock'
   collect2: error: ld returned 1 exit status
   make[3]: *** [<builtin>: vringh_test] Error 1
   ***
   *** The source tree is not clean, please run 'make mrproper'
   *** in /kbuild/worktree/build-ktools-consumer
   ***
   make[5]: *** [/kbuild/worktree/build-ktools-consumer/Makefile:576: outputmakefile] Error 1
   make[4]: *** [Makefile:724: include/config/auto.conf.cmd] Error 2
   make[3]: *** [Makefile:11: mod] Error 2

---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org


                 reply	other threads:[~2022-03-12  4:51 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=202203121220.3s8QdG0u-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=agruenba@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.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