From: Li Fangxu <lifangxu22@gmail.com>
To: acme@kernel.org, namhyung@kernel.org, chenhuacai@loongson.cn
Cc: peterz@infradead.org, mingo@redhat.com, git@xen0n.name,
linux-perf-users@vger.kernel.org, loongarch@lists.linux.dev,
linux-kernel@vger.kernel.org, lifangxu <lifangxu@kylinos.cn>
Subject: [PATCH] perf build: Add rust target flag for loongarch cross compile
Date: Fri, 21 Aug 2026 11:27:02 +0800 [thread overview]
Message-ID: <20260821032702.4258-1-lifangxu22@gmail.com> (raw)
From: lifangxu <lifangxu@kylinos.cn>
Based on commit 30f998c992c9 ("tools build: Fix rust cross
compilation"), add rust target flags for loongarch cross tool to fix
perf compilation error:
*** Unknown rust cross compilation architecture loongarch. Stop.
Signed-off-by: lifangxu <lifangxu@kylinos.cn>
---
tools/perf/Makefile.config | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/perf/Makefile.config b/tools/perf/Makefile.config
index 0ba307e78fe1..42c0ef213750 100644
--- a/tools/perf/Makefile.config
+++ b/tools/perf/Makefile.config
@@ -1149,6 +1149,8 @@ ifndef NO_RUST
RUST_TARGET_FLAGS_s390 := s390x-unknown-linux-gnu
RUST_TARGET_FLAGS_x86 := x86_64-unknown-linux-gnu
RUST_TARGET_FLAGS_x86_64 := x86_64-unknown-linux-gnu
+ RUST_TARGET_FLAGS_loongarch := loongarch64-unknown-linux-gnu
+
ifeq ($(RUST_TARGET_FLAGS_$(ARCH)),)
$(error Unknown rust cross compilation architecture $(ARCH))
--
2.43.0
next reply other threads:[~2026-08-21 3:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 3:27 Li Fangxu [this message]
2026-08-21 3:35 ` [PATCH] perf build: Add rust target flag for loongarch cross compile sashiko-bot
2026-08-21 6:56 ` WANG Rui
2026-08-21 10:38 ` Li Fangxu
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=20260821032702.4258-1-lifangxu22@gmail.com \
--to=lifangxu22@gmail.com \
--cc=acme@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=git@xen0n.name \
--cc=lifangxu@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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).