From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [zen:5.16/bbr2 12/26] tcp_bbr.c:undefined reference to `__udivdi3'
Date: Tue, 11 Jan 2022 08:06:05 +0800 [thread overview]
Message-ID: <202201110739.GCZXHkGM-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]
tree: https://github.com/zen-kernel/zen-kernel 5.16/bbr2
head: c1f95253acc824f05259fbc1a9209991d5719c23
commit: 40c274ef9144f3ad032e482a002461a02829ce1b [12/26] net-tcp: re-generalize TSO sizing in TCP CC module API
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20220111/202201110739.GCZXHkGM-lkp(a)intel.com/config)
compiler: m68k-linux-gcc (GCC) 11.2.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/40c274ef9144f3ad032e482a002461a02829ce1b
git remote add zen https://github.com/zen-kernel/zen-kernel
git fetch --no-tags zen 5.16/bbr2
git checkout 40c274ef9144f3ad032e482a002461a02829ce1b
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=m68k SHELL=/bin/bash
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 >>):
m68k-linux-ld: net/ipv4/tcp_bbr.o: in function `bbr_tso_segs':
>> tcp_bbr.c:(.text+0xf6): undefined reference to `__udivdi3'
m68k-linux-ld: net/ipv4/tcp_bbr.o: in function `bbr_quantization_budget':
tcp_bbr.c:(.text+0x178): undefined reference to `__udivdi3'
m68k-linux-ld: net/ipv4/tcp_bbr.o: in function `bbr_packets_in_net_at_edt':
tcp_bbr.c:(.text+0x2aa): undefined reference to `__udivdi3'
m68k-linux-ld: net/ipv4/tcp_bbr.o: in function `bbr_inflight':
tcp_bbr.c:(.text+0x58c): undefined reference to `__udivdi3'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
reply other threads:[~2022-01-11 0:06 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=202201110739.GCZXHkGM-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.