From: "Björn Töpel" <bjorn@kernel.org>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Mykola Lysenko <mykolal@fb.com>,
bpf@vger.kernel.org, netdev@vger.kernel.org
Cc: "Björn Töpel" <bjorn@rivosinc.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH bpf-next v4 3/3] selftests/bpf: Make install target copy bpftool
Date: Mon, 29 Jan 2024 08:09:16 +0100 [thread overview]
Message-ID: <20240129070916.1639008-4-bjorn@kernel.org> (raw)
In-Reply-To: <20240129070916.1639008-1-bjorn@kernel.org>
From: Björn Töpel <bjorn@rivosinc.com>
bpftool is required for some test_progs tests. Make sure it is
installed as part of the install target.
Signed-off-by: Björn Töpel <bjorn@rivosinc.com>
---
tools/testing/selftests/bpf/Makefile | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/bpf/Makefile b/tools/testing/selftests/bpf/Makefile
index c3c5b85f7dae..ebbb40ef5702 100644
--- a/tools/testing/selftests/bpf/Makefile
+++ b/tools/testing/selftests/bpf/Makefile
@@ -749,8 +749,9 @@ override define INSTALL_RULE
$(DEFAULT_INSTALL_RULE)
@for DIR in $(TEST_INST_SUBDIRS); do \
mkdir -p $(INSTALL_PATH)/$$DIR; \
- rsync -a $(OUTPUT)/$$DIR/*.bpf.o $(INSTALL_PATH)/$$DIR; \
rsync -a --copy-unsafe-links \
+ $(OUTPUT)/$$DIR/*.bpf.o \
+ $(OUTPUT)/$$DIR/bpftool \
$$(/bin/bash -c "echo $(OUTPUT)/$$DIR/$(EXTRA_FILES_GLOB)") \
$(INSTALL_PATH)/$$DIR; \
done
--
2.40.1
prev parent reply other threads:[~2024-01-29 7:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 7:09 [PATCH bpf-next v4 0/3] Fix make install target for BPF selftests Björn Töpel
2024-01-29 7:09 ` [PATCH bpf-next v4 1/3] selftests/bpf: Remove incorrect object path Björn Töpel
2024-01-29 7:09 ` [PATCH bpf-next v4 2/3] selftests/bpf: Make install target copy test_progs extra files Björn Töpel
2024-01-30 0:59 ` Andrii Nakryiko
2024-01-30 6:24 ` Björn Töpel
2024-01-29 7:09 ` Björn Töpel [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=20240129070916.1639008-4-bjorn@kernel.org \
--to=bjorn@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@rivosinc.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mykolal@fb.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).