From: kernel test robot <lkp@intel.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>
Subject: error: A dwo section may not contain relocations
Date: Tue, 6 Jun 2023 16:04:46 +0800 [thread overview]
Message-ID: <202306061557.A6csfwPr-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: f8dba31b0a826e691949cd4fdfa5c30defaac8c5
commit: 61f2b7c7497ba96cdde5bbaeb9e07f4c48f41f97 Makefile.debug: set -g unconditional on CONFIG_DEBUG_INFO_SPLIT
date: 9 months ago
config: riscv-randconfig-r026-20230606 (https://download.01.org/0day-ci/archive/20230606/202306061557.A6csfwPr-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build):
mkdir -p ~/bin
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install riscv cross compiling tool for clang build
# apt-get install binutils-riscv64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=61f2b7c7497ba96cdde5bbaeb9e07f4c48f41f97
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 61f2b7c7497ba96cdde5bbaeb9e07f4c48f41f97
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=riscv olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang ~/bin/make.cross W=1 O=build_dir ARCH=riscv prepare
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/202306061557.A6csfwPr-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error: A dwo section may not contain relocations
>> error: A dwo section may not contain relocations
>> error: A dwo section may not contain relocations
>> error: A dwo section may not contain relocations
>> error: A dwo section may not contain relocations
>> error: A dwo section may not contain relocations
>> error: A dwo section may not contain relocations
>> error: A dwo section may not contain relocations
>> error: A dwo section may not contain relocations
>> error: A dwo section may not contain relocations
>> error: A dwo section may not contain relocations
>> error: A dwo section may not contain relocations
>> error: A dwo section may not contain relocations
>> error: A dwo section may not contain relocations
>> error: A dwo section may not contain relocations
>> error: A dwo section may not contain relocations
>> error: A dwo section may not contain relocations
>> error: A dwo section may not contain relocations
>> error: A dwo section may not contain relocations
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
make[2]: *** [scripts/Makefile.build:249: arch/riscv/kernel/vdso/vgettimeofday.o] Error 1 shuffle=3768112586
make[2]: Target 'include/generated/vdso-offsets.h' not remade because of errors.
make[1]: *** [arch/riscv/Makefile:128: vdso_prepare] Error 2 shuffle=3768112586
make[1]: Target 'prepare' not remade because of errors.
make: *** [Makefile:222: __sub-make] Error 2 shuffle=3768112586
make: Target 'prepare' not remade because of errors.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-06-06 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 8:04 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-08 18:44 error: A dwo section may not contain relocations kernel test robot
2023-08-08 19:46 ` Nick Desaulniers
2023-08-10 7:48 ` Yujie Liu
2023-08-14 22:13 ` Nick Desaulniers
2023-08-16 14:39 ` Philip Li
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=202306061557.A6csfwPr-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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