linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: "lkp@intel.com" <lkp@intel.com>
Cc: "kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
	"andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
	"broonie@kernel.org" <broonie@kernel.org>
Subject: Re: [linux-next:master 1837/11710] sh4-linux-ld: cannot find drivers/spi/.tmp_gl_spi-mux.o: No such file or directory
Date: Wed, 25 Mar 2020 20:30:16 +0000	[thread overview]
Message-ID: <3ec603f5379aafd36f80490ef78108b225eac030.camel@alliedtelesis.co.nz> (raw)
In-Reply-To: <202003260124.NDYYFnCI%lkp@intel.com>

On Thu, 2020-03-26 at 01:38 +0800, kbuild test robot wrote:
> 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
> --

I attempted to reproduce this. The sh4 toolchain was unhappy with my
system (missing libisl.so.22). I bodged something together and got
errors like this all over the place. I also tried the previous commit
and still got the same errors.

>    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@lists.01.org

       reply	other threads:[~2020-03-25 20:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <202003260124.NDYYFnCI%lkp@intel.com>
2020-03-25 20:30 ` Chris Packham [this message]
2020-03-25 20:32   ` [linux-next:master 1837/11710] sh4-linux-ld: cannot find drivers/spi/.tmp_gl_spi-mux.o: No such file or directory Mark Brown
2020-03-26  0:21   ` [kbuild-all] " 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=3ec603f5379aafd36f80490ef78108b225eac030.camel@alliedtelesis.co.nz \
    --to=chris.packham@alliedtelesis.co.nz \
    --cc=andy.shevchenko@gmail.com \
    --cc=broonie@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=lkp@intel.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).