From: Arnd Bergmann <arnd@arndb.de>
To: kbuild-all@lists.01.org
Subject: Re: arm-linux-gnueabi-ld: error: .btf.vmlinux.bin.o is already in final BE8 format
Date: Tue, 14 Jun 2022 18:20:25 +0200 [thread overview]
Message-ID: <CAK8P3a3dvzLhAGV8rdCpX__54vkL0=e5pACUY-es3xiJau=uwg@mail.gmail.com> (raw)
In-Reply-To: <202206120438.Un6Wq4N0-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1974 bytes --]
On Sat, Jun 11, 2022 at 11:00 PM kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 0678afa6055d14799c1dc1eee47c8025eba56cab
> commit: 5d6f52671e76ca2d55d74e676ac4c38ceb14a2d3 ARM: rework endianess selection
> date: 9 weeks ago
> configrong.a.chen(a)intel.com: arm-randconfig-r012-20220612 (https://download.01.org/0day-ci/archive/20220612/202206120438.Un6Wq4N0-lkp(a)intel.com/config)
> compiler: arm-linux-gnueabi-gcc (GCC) 11.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
> # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5d6f52671e76ca2d55d74e676ac4c38ceb14a2d3
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git fetch --no-tags linus master
> git checkout 5d6f52671e76ca2d55d74e676ac4c38ceb14a2d3
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> >> arm-linux-gnueabi-ld: error: .btf.vmlinux.bin.o is already in final BE8 format
> arm-linux-gnueabi-ld: failed to merge target specific data of file .btf.vmlinux.bin.o
I had a look at this bug, and found that this is not caused by my commit, but
rather is the result of CONFIG_CPU_BIG_ENDIAN with BE8 format being
incompatible with CONFIG_DEBUG_INFO_BTF.
I'm sure there is an easy fix but I have not found it. Should we just
add a Kconfig
dependency to prevent this, or does anyone have an idea for a proper fix?
Arnd
next parent reply other threads:[~2022-06-14 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202206120438.Un6Wq4N0-lkp@intel.com>
2022-06-14 16:20 ` Arnd Bergmann [this message]
2022-10-29 20:59 arm-linux-gnueabi-ld: error: .btf.vmlinux.bin.o is already in final BE8 format kernel test robot
2022-11-11 22:16 kernel test robot
2023-01-31 0:50 kernel test robot
2023-03-29 17:54 kernel test robot
2023-09-14 3:45 kernel test robot
2023-09-14 5:08 ` Arnd Bergmann
2023-09-14 10:11 ` Philip Li
2023-09-14 10:16 ` Philip Li
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='CAK8P3a3dvzLhAGV8rdCpX__54vkL0=e5pACUY-es3xiJau=uwg@mail.gmail.com' \
--to=arnd@arndb.de \
--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 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).