From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, llvm@lists.linux.dev
Subject: [android-common:android12-trusty-5.10 1480/7898] ld.lld: error: cannot open /opt/cross/clang-437b7602e4/lib/clang/17/lib/linux/libclang_rt.builtins-x86_64.a: No such file or directory
Date: Wed, 19 Apr 2023 08:08:17 +0800 [thread overview]
Message-ID: <202304190833.IPmAkrxR-lkp@intel.com> (raw)
TO: cros-kernel-buildreports@googlegroups.com
tree: https://android.googlesource.com/kernel/common android12-trusty-5.10
head: 599ad660291e9e6b440d7b25af31d48125b25e88
commit: f14e5bfb39b776318133e00b8c066ce8a870e9ab [1480/7898] ANDROID: Makefile: add compiler-rt dependency explicitly
config: arm-randconfig-r035-20230417 (attached as .config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project 437b7602e4a998220871de78afcb020b9c14a661)
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
# install arm cross compiling tool for clang build
# apt-get install binutils-arm-linux-gnueabi
git remote add android-common https://android.googlesource.com/kernel/common
git fetch --no-tags android-common android12-trusty-5.10
git checkout f14e5bfb39b776318133e00b8c066ce8a870e9ab
# 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=arm olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm distclean
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304190833.IPmAkrxR-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: cannot open /opt/cross/clang-437b7602e4/lib/clang/17/lib/linux/libclang_rt.builtins-x86_64.a: No such file or directory
>> ld.lld: error: cannot open /opt/cross/clang-437b7602e4/lib/clang/17/lib/linux/libclang_rt.builtins-x86_64.a: No such file or directory
>> clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [scripts/Makefile.host:95: scripts/basic/fixdep] Error 1
make[2]: Target '__build' not remade because of errors.
make[1]: *** [Makefile:540: scripts_basic] Error 2
make[1]: Target 'oldconfig' not remade because of errors.
make: *** [Makefile:185: __sub-make] Error 2
make: Target 'oldconfig' not remade because of errors.
--
>> ld.lld: error: cannot open /opt/cross/clang-437b7602e4/lib/clang/17/lib/linux/libclang_rt.builtins-x86_64.a: No such file or directory
>> ld.lld: error: cannot open /opt/cross/clang-437b7602e4/lib/clang/17/lib/linux/libclang_rt.builtins-x86_64.a: No such file or directory
>> clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [scripts/Makefile.host:95: scripts/basic/fixdep] Error 1
make[2]: Target '__build' not remade because of errors.
make[1]: *** [Makefile:540: scripts_basic] Error 2
make[1]: Target 'olddefconfig' not remade because of errors.
make: *** [Makefile:185: __sub-make] Error 2
make: Target 'olddefconfig' not remade because of errors.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-04-19 0:08 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=202304190833.IPmAkrxR-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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 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.