From: Philip Li <philip.li@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kernel test robot <lkp@intel.com>,
<oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: arm-linux-gnueabi-ld: error: .btf.vmlinux.bin.o is already in final BE8 format
Date: Thu, 14 Sep 2023 18:16:31 +0800 [thread overview]
Message-ID: <ZQLdf5hS6j4vtI77@rli9-mobl> (raw)
In-Reply-To: <ZQLcQARpjBzYzgVF@rli9-mobl>
On Thu, Sep 14, 2023 at 06:11:12PM +0800, Philip Li wrote:
> On Thu, Sep 14, 2023 at 07:08:14AM +0200, Arnd Bergmann wrote:
> > On Thu, Sep 14, 2023, at 05:45, kernel test robot wrote:
> > >
> > > If you fix the issue in a separate patch/commit (i.e. not just a new
> > > version of
> > > the same patch/commit), kindly add following tags
> > > | Reported-by: kernel test robot <lkp@intel.com>
> > > | Closes:
> > > https://lore.kernel.org/oe-kbuild-all/202309141131.pNe5J6HH-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
> >
> > It's a completely unrelated issue at the link stage that gets
> > exposed by fixing the other bug. I don't see this in my
>
> Thanks Arnd for the info, we will check and avoid wrong bisection
> for this. Sorry for the noise.
BTW: i found this false positive had been reported multiple times in history,
in your previous reply [0], you had mentioned below to add a Kconfig dependency,
is it the workaround you refer to?
>
> >> 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?
https://lore.kernel.org/oe-kbuild-all/CAK8P3a3dvzLhAGV8rdCpX__54vkL0=e5pACUY-es3xiJau=uwg@mail.gmail.com/
>
> > randconfig builds right now, so I probably have a workaround for
> > it somewhere, but I can't find it.
> >
> > Arnd
next prev parent reply other threads:[~2023-09-14 10:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 3:45 arm-linux-gnueabi-ld: error: .btf.vmlinux.bin.o is already in final BE8 format kernel test robot
2023-09-14 5:08 ` Arnd Bergmann
2023-09-14 10:11 ` Philip Li
2023-09-14 10:16 ` Philip Li [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-29 17:54 kernel test robot
2023-01-31 0:50 kernel test robot
2022-12-20 5:22 kernel test robot
2022-11-11 22:16 kernel test robot
2022-10-29 20:59 kernel test robot
2022-09-10 16:50 kernel test robot
2022-07-16 23:20 kernel test robot
2022-06-11 21:00 kernel test robot
2022-06-14 16:20 ` Arnd Bergmann
2022-06-14 16:20 ` Arnd Bergmann
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=ZQLdf5hS6j4vtI77@rli9-mobl \
--to=philip.li@intel.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.