All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [linux-next:master 1837/11710] sh4-linux-ld: cannot find drivers/spi/.tmp_gl_spi-mux.o: No such file or directory
Date: Thu, 26 Mar 2020 01:38:28 +0800	[thread overview]
Message-ID: <202003260124.NDYYFnCI%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2213 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   bfd7a248502373da8b1c8eb0e811fdb19cc3f8b6
commit: e9e40543ad5b38b848879768359fd13650529961 [1837/11710] spi: Add generic SPI multiplexer
config: sh-randconfig-a001-20200325 (attached as .config)
compiler: sh4-linux-gcc (GCC) 9.2.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 e9e40543ad5b38b848879768359fd13650529961
        # save the attached .config to linux build tree
        GCC_VERSION=9.2.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/spi/.tmp_gl_spi-mux.o: No such file or directory
>> sh4-linux-objcopy: 'drivers/spi/.tmp_mx_spi-mux.o': No such file
   rm: cannot remove 'drivers/spi/.tmp_gl_spi-mux.o': No such file or directory
   rm: cannot remove 'drivers/spi/.tmp_mx_spi-mux.o': No such file or directory
--
   sh4-linux-objcopy: Unable to change endianness of input file(s)
>> sh4-linux-ld: cannot find drivers/mux/.tmp_gl_core.o: No such file or directory
>> sh4-linux-objcopy: 'drivers/mux/.tmp_mx_core.o': No such file
   rm: cannot remove 'drivers/mux/.tmp_gl_core.o': No such file or directory
   rm: cannot remove 'drivers/mux/.tmp_mx_core.o': No such file or directory
--
   sh4-linux-objcopy: Unable to change endianness of input file(s)
>> sh4-linux-ld: cannot find drivers/mux/.tmp_gl_adg792a.o: No such file or directory
>> sh4-linux-objcopy: 'drivers/mux/.tmp_mx_adg792a.o': No such file
   rm: cannot remove 'drivers/mux/.tmp_gl_adg792a.o': No such file or directory
   rm: cannot remove 'drivers/mux/.tmp_mx_adg792a.o': No such file or directory
--
>> sh4-linux-ar: drivers/mux/core.o: No such file or directory
--
>> sh4-linux-ld: cannot find drivers/mux/adg792a.o: No such file or directory

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 26822 bytes --]

             reply	other threads:[~2020-03-25 17:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 17:38 kbuild test robot [this message]
2020-03-25 20:30 ` [linux-next:master 1837/11710] sh4-linux-ld: cannot find drivers/spi/.tmp_gl_spi-mux.o: No such file or directory Chris Packham
2020-03-25 20:30   ` Chris Packham
2020-03-25 20:32   ` Mark Brown
2020-03-25 20:32     ` Mark Brown
2020-03-26  0:21   ` [kbuild-all] " Rong Chen
2020-03-26  0:21     ` Rong Chen

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=202003260124.NDYYFnCI%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.