From: kernel test robot <lkp@intel.com>
To: Alexei Starovoitov <ast@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>
Subject: collect2: error: ld returned 1 exit status
Date: Sun, 30 Jan 2022 05:57:12 +0800 [thread overview]
Message-ID: <202201300518.Q1ZGEJYY-lkp@intel.com> (raw)
Hi Alexei,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: cb323ee75d24e7acc2f188d123ba6df46159cf09
commit: d71fa5c9763c24dd997a2fa4feb7a13a95bab42c bpf: Add kernel module with user mode driver that populates bpffs.
date: 1 year, 5 months ago
config: i386-randconfig-m021 (https://download.01.org/0day-ci/archive/20220130/202201300518.Q1ZGEJYY-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d71fa5c9763c24dd997a2fa4feb7a13a95bab42c
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout d71fa5c9763c24dd997a2fa4feb7a13a95bab42c
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=i386 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 >>):
/usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libelf.so when searching for -lelf
/usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libelf.a when searching for -lelf
/usr/bin/ld: cannot find -lelf
/usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libelf.so when searching for -lelf
/usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libz.so when searching for -lz
/usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libz.a when searching for -lz
/usr/bin/ld: cannot find -lz
/usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/libz.so when searching for -lz
>> collect2: error: ld returned 1 exit status
---
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-29 21:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 21:57 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-25 19:17 collect2: error: ld returned 1 exit status kernel test robot
2021-09-11 19:31 kernel test robot
2021-07-20 19:27 kernel test robot
2021-07-05 2:19 kernel test robot
2021-05-31 12:45 kernel test robot
2021-05-29 19:48 kernel test robot
2021-05-16 23:06 kernel test robot
2021-04-10 19:46 kernel test robot
2021-03-07 17:24 kernel test robot
2021-03-03 21:22 kernel test robot
2019-05-31 6:18 kbuild test robot
2017-02-12 4:37 kbuild test robot
2017-01-01 19:08 kbuild test robot
2016-12-11 10:05 kbuild test robot
2016-11-20 20:39 kbuild test robot
2016-11-21 10:16 ` Linus Walleij
2016-09-11 2:06 kbuild test robot
2016-04-16 23:50 kbuild test robot
2016-04-03 0:46 kbuild test robot
2016-03-12 23:33 kbuild test robot
2016-03-05 23:34 kbuild test robot
2016-02-27 23:12 kbuild test robot
2016-01-16 23:31 kbuild test robot
2015-12-05 23:55 kbuild test robot
2015-11-22 1:05 kbuild test robot
2015-11-23 9:54 ` Michael Ellerman
2015-11-23 12:45 ` Fengguang Wu
2015-10-10 23:32 kbuild test robot
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=202201300518.Q1ZGEJYY-lkp@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).