From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [hch-block:block-kill-bd_inode 5/40] block2mtd.c:undefined reference to `__umoddi3'
Date: Tue, 12 Oct 2021 20:58:52 +0800 [thread overview]
Message-ID: <202110122046.UExnIitd-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1500 bytes --]
tree: git://git.infradead.org/users/hch/block.git block-kill-bd_inode
head: ffeb1c3218d3511f9972cc09dfe37a29c0da40cb
commit: e774673fc5332e888028f74b7e83c9797c432395 [5/40] mtd/block2mtd: use bdev_nr_sectors instead of open coding it
config: m68k-randconfig-r002-20211012 (attached as .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
git remote add hch-block git://git.infradead.org/users/hch/block.git
git fetch --no-tags hch-block block-kill-bd_inode
git checkout e774673fc5332e888028f74b7e83c9797c432395
# save the attached .config 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: arch/m68k/kernel/uboot.o: in function `process_uboot_commandline':
uboot.c:(.init.text+0x30): undefined reference to `_init_sp'
m68k-linux-ld: drivers/mtd/devices/block2mtd.o: in function `add_device.constprop.0.isra.0':
>> block2mtd.c:(.text+0x3fc): undefined reference to `__umoddi3'
---
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: 26635 bytes --]
reply other threads:[~2021-10-12 12: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=202110122046.UExnIitd-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.