From: patchwork-bot+netdevbpf@kernel.org
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, shuah@kernel.org,
quentin@isovalent.com, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf] tools/runqslower: Fix cross-build
Date: Fri, 12 Nov 2021 21:00:07 +0000 [thread overview]
Message-ID: <163675080746.17861.4035490534028049921.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211112155128.565680-1-jean-philippe@linaro.org>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Fri, 12 Nov 2021 15:51:30 +0000 you wrote:
> Commit be79505caf3f ("tools/runqslower: Install libbpf headers when
> building") uses the target libbpf to build the host bpftool, which
> doesn't work when cross-building:
>
> make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -C tools/bpf/runqslower O=/tmp/runqslower
> ...
> LINK /tmp/runqslower/bpftool/bpftool
> /usr/bin/ld: /tmp/runqslower/libbpf/libbpf.a(libbpf-in.o): Relocations in generic ELF (EM: 183)
> /usr/bin/ld: /tmp/runqslower/libbpf/libbpf.a: error adding symbols: file in wrong format
> collect2: error: ld returned 1 exit status
>
> [...]
Here is the summary with links:
- [bpf] tools/runqslower: Fix cross-build
https://git.kernel.org/bpf/bpf/c/c9213bcf2fe1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-11-12 21:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 15:51 [PATCH bpf] tools/runqslower: Fix cross-build Jean-Philippe Brucker
2021-11-12 16:17 ` Quentin Monnet
2021-11-12 16:28 ` Jean-Philippe Brucker
2021-11-16 6:10 ` Andrii Nakryiko
2021-11-16 8:39 ` Jean-Philippe Brucker
2021-11-16 19:03 ` Andrii Nakryiko
2021-11-12 21:00 ` patchwork-bot+netdevbpf [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=163675080746.17861.4035490534028049921.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jean-philippe@linaro.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=quentin@isovalent.com \
--cc=shuah@kernel.org \
--cc=songliubraving@fb.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