From: Takashi Iwai <tiwai@suse.de>
To: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
Cc: kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Takashi Iwai <tiwai@suse.de>
Subject: Re: [linux-next:master 2420/3030] ld.lld: error: undefined symbol: __udivdi3
Date: Wed, 17 May 2023 16:41:12 +0200 [thread overview]
Message-ID: <87lehn10mv.wl-tiwai@suse.de> (raw)
In-Reply-To: <202305171622.jKTovBvy-lkp@intel.com>
On Wed, 17 May 2023 11:16:01 +0200,
kernel test robot wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 065efa589871e93b6610c70c1e9de274ef1f1ba2
> commit: bb5ceb43b7bfa166fd5d739d51ad46c1cfb225e3 [2420/3030] ALSA: emu10k1: fix non-zero mixer control defaults in highres mode
> config: i386-buildonly-randconfig-r001-20230515
> compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
> 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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=bb5ceb43b7bfa166fd5d739d51ad46c1cfb225e3
> 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 bb5ceb43b7bfa166fd5d739d51ad46c1cfb225e3
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 olddefconfig
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202305171622.jKTovBvy-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> ld.lld: error: undefined symbol: __udivdi3
> >>> referenced by emufx.c:1146 (sound/pci/emu10k1/emufx.c:1146)
> >>> sound/pci/emu10k1/emufx.o:(snd_emu10k1_init_stereo_control) in archive vmlinux.a
> >>> referenced by emufx.c:1124 (sound/pci/emu10k1/emufx.c:1124)
> >>> sound/pci/emu10k1/emufx.o:(snd_emu10k1_init_mono_control) in archive vmlinux.a
This comes from the division of 64bit values. It has to be replaced
with div64*() macro.
Oswald, could you check it?
thanks,
Takashi
prev parent reply other threads:[~2023-05-17 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 9:16 kernel test robot
2023-05-17 14:41 ` Takashi Iwai [this message]
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=87lehn10mv.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oswald.buddenhagen@gmx.de \
/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