From: kernel test robot <lkp@intel.com>
To: Vincent Chen <vincent.chen@sifive.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Palmer Dabbelt <palmerdabbelt@google.com>,
Atish Patra <atish.patra@wdc.com>
Subject: riscv64-linux-objcopy: 'arch/riscv/kernel/vdso/vdso.so.dbg': No such file
Date: Sat, 20 Jun 2020 18:11:32 +0800 [thread overview]
Message-ID: <202006201829.cD1eClfJ%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
Hi Vincent,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 4333a9b0b67bb4e8bcd91bdd80da80b0ec151162
commit: ad5d1122b82fbd6a816d1b9d26ee01a6dbc2d757 riscv: use vDSO common flow to reduce the latency of the time-related functions
date: 9 days ago
config: riscv-randconfig-r023-20200619 (attached as .config)
compiler: riscv64-linux-gcc (GCC) 9.3.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
git checkout ad5d1122b82fbd6a816d1b9d26ee01a6dbc2d757
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv
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 >>):
>> riscv64-linux-objcopy: 'arch/riscv/kernel/vdso/vdso.so.dbg': No such file
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 27676 bytes --]
next reply other threads:[~2020-06-20 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 10:11 kernel test robot [this message]
2020-06-20 12:20 ` riscv64-linux-objcopy: 'arch/riscv/kernel/vdso/vdso.so.dbg': No such file Vincent Chen
-- strict thread matches above, loose matches on Subject: below --
2020-06-15 6:19 kernel 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=202006201829.cD1eClfJ%lkp@intel.com \
--to=lkp@intel.com \
--cc=atish.patra@wdc.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=palmerdabbelt@google.com \
--cc=vincent.chen@sifive.com \
/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).