From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: sedat.dilek@gmail.com
Cc: linux-trace-devel@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
linux-kbuild@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [Linux v5.19-rc2] rtla: Errors when running `make tools/clean`
Date: Thu, 30 Jun 2022 11:57:39 +0200 [thread overview]
Message-ID: <178bee80-3ccc-812a-2e2e-46540bbdcc51@kernel.org> (raw)
In-Reply-To: <CA+icZUWFUC5eiKS96vpoPQbX+jx5OYBfD40Ns86sUxE0hcft1w@mail.gmail.com>
Hi Sedat,
On 6/27/22 08:23, Sedat Dilek wrote:
> On Wed, Jun 15, 2022 at 12:23 AM Sedat Dilek <sedat.dilek@gmail.com> wrote:
>> [ CC linux-kbuild folks ]
>>
>> Hi,
>>
>> while digging into a perf issue I see this:
>>
>> $ cd /path/to/linux.git
>>
>> $ LC_ALL=C make -C tools/ clean 2>&1 | tee ../make-log_tools-clean.txt
>> ...
Do you mind trying this?
diff --git a/tools/tracing/rtla/Makefile b/tools/tracing/rtla/Makefile
index 3822f4ea5f49..1bea2d16d4c1 100644
--- a/tools/tracing/rtla/Makefile
+++ b/tools/tracing/rtla/Makefile
@@ -1,6 +1,6 @@
NAME := rtla
# Follow the kernel version
-VERSION := $(shell cat VERSION 2> /dev/null || make -sC ../../.. kernelversion)
+VERSION := $(shell cat VERSION 2> /dev/null || make -sC ../../.. kernelversion | grep -v make)
# From libtracefs:
# Makefiles suck: This macro sets a default value of $(2) for the
next prev parent reply other threads:[~2022-06-30 9:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 22:23 [Linux v5.19-rc2] rtla: Errors when running `make tools/clean` Sedat Dilek
2022-06-27 6:23 ` Sedat Dilek
2022-06-30 9:57 ` Daniel Bristot de Oliveira [this message]
2022-07-01 8:08 ` Sedat Dilek
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=178bee80-3ccc-812a-2e2e-46540bbdcc51@kernel.org \
--to=bristot@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sedat.dilek@gmail.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).