From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: bpf <bpf@vger.kernel.org>, iii@linux.ibm.com
Subject: selftests/bpf - Error: failed to open BPF object file: Endian mismatch
Date: Fri, 2 Apr 2021 09:48:36 +0200 [thread overview]
Message-ID: <21e66a09-514f-f426-b9e2-13baab0b938b@csgroup.eu> (raw)
Hello,
I'm having hard time cross-building bpf selftests on an x86 for a powerpc target.
[root@PC-server-ldb bpf]# make CROSS_COMPILE=ppc-linux- ARCH=powerpc V=1
/root/gen_ldb/linux-powerpc/tools/testing/selftests/bpf/host-tools/sbin/bpftool gen skeleton
/root/gen_ldb/linux-powerpc/tools/testing/selftests/bpf/atomic_bounds.o >
/root/gen_ldb/linux-powerpc/tools/testing/selftests/bpf/atomic_bounds.skel.h
libbpf: elf: endianness mismatch in atomic_bounds.
Error: failed to open BPF object file: Endian mismatch
[root@PC-server-ldb bpf]# file atomic_bounds.o
atomic_bounds.o: ELF 64-bit MSB relocatable, eBPF, version 1 (SYSV), with debug_info, not stripped
Seems like the just-built host bpftool doesn't take into account target's endianness.
I see the patch https://github.com/torvalds/linux/commit/313e7f6f ("selftest/bpf: Use -m{little,
big}-endian for clang") in bpf selftest to enable cross-compilation, but it seems it is not enough.
What should I do to get bpftool work with the target's endianness ?
Thanks
Christophe
next reply other threads:[~2021-04-02 7:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 7:48 Christophe Leroy [this message]
2021-04-02 8:02 ` selftests/bpf - Error: failed to open BPF object file: Endian mismatch Christophe Leroy
2021-04-03 16:01 ` Andrii Nakryiko
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=21e66a09-514f-f426-b9e2-13baab0b938b@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=bpf@vger.kernel.org \
--cc=iii@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).