From: Namhyung Kim <namhyung@kernel.org>
To: hev <r@hev.cc>
Cc: jiny L <leeavianna3@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
loongarch@lists.linux.dev
Subject: Re: [PATCH] perf loongarch: Fix build failure with CONFIG_LIBDW_DWARF_UNWIND
Date: Mon, 13 Apr 2026 23:47:10 -0700 [thread overview]
Message-ID: <ad3i7q62HSEYT1up@google.com> (raw)
In-Reply-To: <CAHirt9jA3G5kRjJbmosttEDkvZhKfx3U6oa63JZOnpEx4Cqb2g@mail.gmail.com>
On Tue, Apr 14, 2026 at 09:18:18AM +0800, hev wrote:
> On Tue, Apr 14, 2026 at 9:13 AM jiny L <leeavianna3@gmail.com> wrote:
> >
> >
> >
> > On Mon, Apr 13, 2026 at 5:52 PM WANG Rui <r@hev.cc> wrote:
> >>
> >> Building perf for LoongArch fails when CONFIG_LIBDW_DWARF_UNWIND is
> >> enabled because unwind-libdw.o is still referenced in
> >> arch/loongarch/util/Build.
> >>
> >> Fixes: e62fae9d9e8 ("perf unwind-libdw: Fix a cross-arch unwinding bug")
> >> Signed-off-by: WANG Rui <r@hev.cc>
> >> ---
> >> tools/perf/arch/loongarch/util/Build | 1 -
> >> 1 file changed, 1 deletion(-)
> >>
> >> diff --git a/tools/perf/arch/loongarch/util/Build b/tools/perf/arch/loongarch/util/Build
> >> index 3ad73d0289f3..8d91e78d31c9 100644
> >> --- a/tools/perf/arch/loongarch/util/Build
> >> +++ b/tools/perf/arch/loongarch/util/Build
> >> @@ -1,4 +1,3 @@
> >> perf-util-y += header.o
> >>
> >> perf-util-$(CONFIG_LOCAL_LIBUNWIND) += unwind-libunwind.o
> >> -perf-util-$(CONFIG_LIBDW_DWARF_UNWIND) += unwind-libdw.o
> >> --
> >> 2.53.0
> >>
> >>
> >
> > I happened to have the same build issue on linux 7.0 and I found there is already a patch fixing this https://lore.kernel.org/lkml/20260413024805.1316480-3-irogers@google.com/
>
> Thanks for the reference.
> Rui
As the Ian's series is still under review, I'd pick this one instead.
Thanks,
Namhyung
next prev parent reply other threads:[~2026-04-14 6:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 0:51 [PATCH] perf loongarch: Fix build failure with CONFIG_LIBDW_DWARF_UNWIND WANG Rui
[not found] ` <CANVb8WZXZj1Yqd7foqHBLSHjO73r0Kg62bMbrb--aE8wR3G2hg@mail.gmail.com>
2026-04-14 1:18 ` hev
2026-04-14 6:47 ` Namhyung Kim [this message]
2026-04-14 7:12 ` Huacai Chen
2026-04-14 17:12 ` Namhyung Kim
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=ad3i7q62HSEYT1up@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=leeavianna3@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=r@hev.cc \
/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