From: Nathan Chancellor <nathan@kernel.org>
To: Wedson Almeida Filho <wedsonaf@google.com>,
Miguel Ojeda <ojeda@kernel.org>
Cc: kbuild-all@lists.01.org, llvm@lists.linux.dev,
kernel test robot <lkp@intel.com>,
rust-for-linux@vger.kernel.org
Subject: Re: [ojeda-linux:rust-next 18/20] ld.lld: error: drivers/built-in.a(gpio/gpio_pl061_rust.o) is incompatible with aarch64elfb
Date: Sat, 12 Feb 2022 12:54:32 -0700 [thread overview]
Message-ID: <YggQeC0PuAseqtpQ@archlinux-ax161> (raw)
In-Reply-To: <202202121743.YbGELjcY-lkp@intel.com>
+ Miguel, Wedson, rust-for-linux, since it looks like this did not get
sent to you all.
Possibly some incompatibility with Rust + aarch64be?
Cheers,
Nathan
On Sat, Feb 12, 2022 at 06:39:33PM +0800, kernel test robot wrote:
> CC: linux-kernel@vger.kernel.org
> TO: Wedson Almeida Filho <wedsonaf@google.com>
> CC: Miguel Ojeda <ojeda@kernel.org>
>
> Hi Wedson,
>
> First bad commit (maybe != root cause):
>
> tree: https://github.com/ojeda/linux.git rust-next
> head: ced9f62ec4355bbb92226ac3f019da468a5c996b
> commit: 5c1fec092f967b9b4722f6d91c9bcbe8222098fd [18/20] [RFC] drivers: gpio: PrimeCell PL061 in Rust
> config: arm64-randconfig-r033-20220212 (https://download.01.org/0day-ci/archive/20220212/202202121743.YbGELjcY-lkp@intel.com/config)
> compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project f6685f774697c85d6a352dcea013f46a99f9fe31)
> 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
> # install arm64 cross compiling tool for clang build
> # apt-get install binutils-aarch64-linux-gnu
> # https://github.com/ojeda/linux/commit/5c1fec092f967b9b4722f6d91c9bcbe8222098fd
> git remote add ojeda-linux https://github.com/ojeda/linux.git
> git fetch --no-tags ojeda-linux rust-next
> git checkout 5c1fec092f967b9b4722f6d91c9bcbe8222098fd
> # save the config file to linux build tree
> mkdir build_dir
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm64 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 >>):
>
> ld.lld: error: rust/built-in.a(core.o) is incompatible with aarch64elfb
> ld.lld: error: rust/built-in.a(compiler_builtins.o) is incompatible with aarch64elfb
> ld.lld: error: rust/built-in.a(alloc.o) is incompatible with aarch64elfb
> ld.lld: error: rust/built-in.a(kernel.o) is incompatible with aarch64elfb
> >> ld.lld: error: drivers/built-in.a(gpio/gpio_pl061_rust.o) is incompatible with aarch64elfb
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
>
next prev parent reply other threads:[~2022-02-12 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 10:39 [ojeda-linux:rust-next 18/20] ld.lld: error: drivers/built-in.a(gpio/gpio_pl061_rust.o) is incompatible with aarch64elfb kernel test robot
2022-02-12 19:54 ` Nathan Chancellor [this message]
2022-02-12 22:37 ` Miguel Ojeda
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=YggQeC0PuAseqtpQ@archlinux-ax161 \
--to=nathan@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@google.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