From: Vicki Pfau <vi@endrift.com>
To: Jiri Olsa <olsajiri@gmail.com>
Cc: Alexandre Peixoto Ferreira <alexandref75@gmail.com>,
Jiri Olsa <olsajiri@gmail.com>, Daniel Xu <dxu@dxuuu.xyz>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: Kernel build fail with 'btf_encoder__encode: btf__dedup failed!'
Date: Wed, 8 Feb 2023 16:21:15 -0800 [thread overview]
Message-ID: <20230209002115.GA15810@debian> (raw)
In-Reply-To: <Y9kxUzyfpEQpnN7w@krava>
Hello,
I seem to be having a related problem trying to build Linux at all. This used
to work, but after some recent upgrades (I am also running Arch Linux), I'm
getting a dedup error too. I'm also getting a "relocation to !ENDBR" error
that, as far as I can tell (and that's not particularly far, to be fair), is
erroneous, which makes me think something even stranger is going on with my
tools. Since both of these issues appeared, so far, only on Arch Linux, it
might be an Arch-speciifc packaging issue.
I've uploaded my config and pahole log to the following URLs:
https://endrift.com/files/config.gz
https://endrift.com/files/make-log.xz
Vicki
PS: My apologies for the lack of a quoted reply or any other formatting issues;
I'm not subscribed to this mailing list and am struggling to figure out how to
send a reply without the originals in my client. In retrospect, maybe I could
have imported the .eml/mbox directly.
next prev parent reply other threads:[~2023-02-09 0:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 17:48 Kernel build fail with 'btf_encoder__encode: btf__dedup failed!' Daniel Xu
2023-01-22 21:25 ` Daniel Xu
2023-01-23 8:06 ` Jiri Olsa
2023-01-24 6:13 ` Daniel Xu
2023-01-27 22:28 ` Alexandre Peixoto Ferreira
2023-01-28 0:00 ` Jiri Olsa
2023-01-28 0:21 ` Daniel Xu
2023-01-28 0:23 ` Daniel Xu
2023-01-28 19:23 ` Alexandre Peixoto Ferreira
2023-01-31 15:18 ` Jiri Olsa
2023-02-09 0:21 ` Vicki Pfau [this message]
2023-02-09 4:15 ` Alexandre Peixoto Ferreira
2023-02-09 13:07 ` Alan Maguire
2023-02-10 14:02 ` Alexandre Peixoto Ferreira
2023-02-10 14:34 ` Jiri Olsa
2023-02-10 15:37 ` Alexandre Ferreira
2023-02-14 6:33 ` Tianyi Liu
2023-04-11 17:00 ` [PATCH] vmlinux.lds.h: Force-align ELF notes section to four bytes Josh Poimboeuf
2023-04-12 7:10 ` Tianyi Liu
2023-04-12 16:30 ` Josh Poimboeuf
2023-04-13 2:21 ` Joan Bruguera Micó
2023-04-13 9:23 ` Tianyi Liu
2023-04-13 18:59 ` [PATCH] vmlinux.lds.h: Discard .note.gnu.property section Josh Poimboeuf
2023-04-16 19:02 ` Joan Bruguera Micó
2023-04-18 21:47 ` Josh Poimboeuf
2023-04-18 21:49 ` [PATCH v2] " Josh Poimboeuf
2023-04-13 4:54 ` [PATCH] vmlinux.lds.h: Force-align ELF notes section to four bytes Tianyi Liu
2023-04-16 18:52 ` Joan Bruguera Micó
2023-04-27 5:14 ` Joan Bruguera Micó
2023-05-18 11:00 ` [tip: objtool/urgent] vmlinux.lds.h: Discard .note.gnu.property section tip-bot2 for Josh Poimboeuf
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=20230209002115.GA15810@debian \
--to=vi@endrift.com \
--cc=acme@kernel.org \
--cc=alexandref75@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=dxu@dxuuu.xyz \
--cc=olsajiri@gmail.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 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.