From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [linux-next:master 961/11283] sh4-linux-ld: cannot find drivers/dma-buf/.tmp_gl_dma-resv.o: No such file or directory
Date: Mon, 27 Jan 2020 05:01:03 +0800 [thread overview]
Message-ID: <202001270500.MBmFuiSc%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 702ccea170f07783bd002055a353a0866c062267
commit: ffbbaa7420f7a7ee6d547cd9adc286fe2e3753e0 [961/11283] dma_resv: prime lockdep annotations
config: sh-randconfig-a001-20200126 (attached as .config)
compiler: sh4-linux-gcc (GCC) 7.5.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout ffbbaa7420f7a7ee6d547cd9adc286fe2e3753e0
# save the attached .config to linux build tree
GCC_VERSION=7.5.0 make.cross ARCH=sh
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
sh4-linux-objcopy: Unable to change endianness of input file(s)
>> sh4-linux-ld: cannot find drivers/dma-buf/.tmp_gl_dma-resv.o: No such file or directory
>> sh4-linux-objcopy: 'drivers/dma-buf/.tmp_mx_dma-resv.o': No such file
rm: cannot remove 'drivers/dma-buf/.tmp_gl_dma-resv.o': No such file or directory
rm: cannot remove 'drivers/dma-buf/.tmp_mx_dma-resv.o': No such file or directory
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 22378 bytes --]
reply other threads:[~2020-01-26 21:01 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=202001270500.MBmFuiSc%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.