From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [esmil:visionfive 36/74] pwm-sifive-ptc.c:undefined reference to `__udivdi3'
Date: Fri, 28 Jan 2022 08:44:56 +0800 [thread overview]
Message-ID: <202201280855.Boip1DFz-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]
tree: https://github.com/esmil/linux visionfive
head: 31606e93b454de33cd75c74d622f35eee020dc5b
commit: d8f87b24049876b29ade8ed4e49f975d32eeec79 [36/74] drivers/pwm: Add SiFive PWM PTC driver
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20220128/202201280855.Boip1DFz-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/esmil/linux/commit/d8f87b24049876b29ade8ed4e49f975d32eeec79
git remote add esmil https://github.com/esmil/linux
git fetch --no-tags esmil visionfive
git checkout d8f87b24049876b29ade8ed4e49f975d32eeec79
# 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: drivers/pwm/pwm-sifive-ptc.o: in function `sifive_pwm_ptc_apply':
>> pwm-sifive-ptc.c:(.text+0x1c2): undefined reference to `__udivdi3'
`.exit.text' referenced in section `.data' of sound/soc/codecs/tlv320adc3xxx.o: defined in discarded section `.exit.text' of sound/soc/codecs/tlv320adc3xxx.o
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Chenjieqin <Jessica.Chen@starfivetech.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Emil Renner Berthing <kernel@esmil.dk>
Subject: [esmil:visionfive 36/74] pwm-sifive-ptc.c:undefined reference to `__udivdi3'
Date: Fri, 28 Jan 2022 08:44:56 +0800 [thread overview]
Message-ID: <202201280855.Boip1DFz-lkp@intel.com> (raw)
tree: https://github.com/esmil/linux visionfive
head: 31606e93b454de33cd75c74d622f35eee020dc5b
commit: d8f87b24049876b29ade8ed4e49f975d32eeec79 [36/74] drivers/pwm: Add SiFive PWM PTC driver
config: m68k-allyesconfig (https://download.01.org/0day-ci/archive/20220128/202201280855.Boip1DFz-lkp@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/esmil/linux/commit/d8f87b24049876b29ade8ed4e49f975d32eeec79
git remote add esmil https://github.com/esmil/linux
git fetch --no-tags esmil visionfive
git checkout d8f87b24049876b29ade8ed4e49f975d32eeec79
# 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: drivers/pwm/pwm-sifive-ptc.o: in function `sifive_pwm_ptc_apply':
>> pwm-sifive-ptc.c:(.text+0x1c2): undefined reference to `__udivdi3'
`.exit.text' referenced in section `.data' of sound/soc/codecs/tlv320adc3xxx.o: defined in discarded section `.exit.text' of sound/soc/codecs/tlv320adc3xxx.o
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next reply other threads:[~2022-01-28 0:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 0:44 kernel test robot [this message]
2022-01-28 0:44 ` [esmil:visionfive 36/74] pwm-sifive-ptc.c:undefined reference to `__udivdi3' kernel test robot
2022-01-29 16:15 ` Geert Uytterhoeven
2022-01-29 16:15 ` Geert Uytterhoeven
2022-01-29 16:35 ` Emil Renner Berthing
2022-01-29 16:35 ` Emil Renner Berthing
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=202201280855.Boip1DFz-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.