From: Dominique Martinet <asmadeus@codewreck.org>
To: dwarves@vger.kernel.org, Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: pahole split BTF support broken on 32bit builds?
Date: Mon, 11 Jul 2022 10:28:16 +0900 [thread overview]
Message-ID: <Yst8sOnzw+YZRRkE@codewreck.org> (raw)
In-Reply-To: <YsrXjggSxfe2U7Oz@codewreck.org>
Dominique Martinet wrote on Sun, Jul 10, 2022 at 10:43:42PM +0900:
> I could reproduce by just building any kernel with ARCH=i386 and using a
> 32bit pahole
>
> $ LD_LIBRARY_PATH=/tmp/pahole/build /tmp/pahole/build/pahole -J --btf_base vmlinux arch/x86/crypto/aesni-intel.ko
> Failed to parse base BTF 'vmlinux': -22
>
> $ file /tmp/pahole/build/pahole
> /tmp/pahole/build/pahole: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /nix/store/pp1yzf2flqnjm02jnjcgxhx015bhmi9j-glibc-2.34-210/lib/ld-linux.so.2, for GNU/Linux 2.6.32, with debug_info, not stripped
Some more infos: this actually just got fixed by mistake when I changed
libbpf build to use elfutils instead of the old libelf
That was a side-product of the 0.8.0 upgrade which took a bit of time to
get merged, as that wouldn't build anymore with old libelf (can't
remember what, something missing)...
So, well, I guess it's probably not worth looking too far as that's
unlikely to be a problem again, and I'm not sure if libelf is still
maintained.
Sorry for the noise.
--
Dominique
prev parent reply other threads:[~2022-07-11 1:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 13:43 pahole split BTF support broken on 32bit builds? Dominique Martinet
2022-07-11 1:28 ` Dominique Martinet [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=Yst8sOnzw+YZRRkE@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=acme@kernel.org \
--cc=dwarves@vger.kernel.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