public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: ast@kernel.org, yhs@fb.com, sean.wang@mediatek.com,
	Linux List Kernel Mailing <linux-kernel@vger.kernel.org>
Subject: Re: Unable bisect issue because kernel not building from old commits
Date: Sun, 25 Sep 2022 20:43:33 +0200	[thread overview]
Message-ID: <20220925184333.GA13967@1wt.eu> (raw)
In-Reply-To: <CABXGCsN532FpFraXu_DiA4_SiRRXqy6zL0AD+oV0c5er4DJQJQ@mail.gmail.com>

On Sun, Sep 25, 2022 at 09:13:13PM +0500, Mikhail Gavrilov wrote:
> On Sun, Sep 25, 2022 at 8:21 PM Willy Tarreau <w@1wt.eu> wrote:
> > Just add:
> >
> >    CROSS_COMPILE=/path/to/toolchain/bin/prefix-
> >
> > to your make command line and it will be fine.
> >
> > The makefile will append {gcc,ld,...} to this CROSS_COMPILE prefix to
> > construct the full pathname to the binaries.
> 
> It works!
> But I hit another build issue.
> 
> $ make clean &&
> CROSS_COMPILE=~/Downloads/x86_64-gcc-7.5.0-nolibc-x86_64-linux/gcc-7.5.0-nolibc/x86_64-linux/bin/x86_64-linux-
> make -j32 bzImage
> ***
>   GEN     modules.builtin
>   LD      .tmp_vmlinux.btf
>   BTF     .btf.vmlinux.bin.o
>   LD      .tmp_vmlinux.kallsyms1
>   KSYMS   .tmp_vmlinux.kallsyms1.S
>   AS      .tmp_vmlinux.kallsyms1.S
>   LD      .tmp_vmlinux.kallsyms2
>   KSYMS   .tmp_vmlinux.kallsyms2.S
>   AS      .tmp_vmlinux.kallsyms2.S
>   LD      vmlinux
>   BTFIDS  vmlinux
> FAILED: load BTF from vmlinux: Invalid argument
> make: *** [Makefile:1159: vmlinux] Error 255
> make: *** Deleting file 'vmlinux'

This was reported and addressed a month ago:

    https://lore.kernel.org/bpf/20220825171620.cioobudss6ovyrkc@altlinux.org/t/#m24a9de4b8cc11eb9c3bbed022487d6de0d42ea4b

In short if you don't need XDP you could possibly disable
CONFIG_DEBUG_INFO_BTF, otherwise you may have to rebuild the latest
pahole utility that seems to be involved in this. But I never faced
this issue so I can only recommend hints about things to look at,
and could be wrong.

Willy

      reply	other threads:[~2022-09-25 18:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-24 22:22 Unable bisect issue because kernel not building from old commits Mikhail Gavrilov
2022-09-25  4:20 ` Willy Tarreau
2022-09-25 14:02   ` Mikhail Gavrilov
2022-09-25 15:21     ` Willy Tarreau
2022-09-25 16:13       ` Mikhail Gavrilov
2022-09-25 18:43         ` Willy Tarreau [this message]

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=20220925184333.GA13967@1wt.eu \
    --to=w@1wt.eu \
    --cc=ast@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikhail.v.gavrilov@gmail.com \
    --cc=sean.wang@mediatek.com \
    --cc=yhs@fb.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