From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: James Clark <james.clark@arm.com>,
jolsa@kernel.org, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tools build: Fix feature detect clean for out of source builds
Date: Wed, 1 Sep 2021 11:26:28 -0300 [thread overview]
Message-ID: <YS+NlBGl1xMqHlgC@kernel.org> (raw)
In-Reply-To: <YS548qYreGLtabs4@krava>
Em Tue, Aug 31, 2021 at 08:46:10PM +0200, Jiri Olsa escreveu:
> On Mon, Aug 16, 2021 at 02:07:05PM +0100, James Clark wrote:
> > Currently the clean target when using O= isn't cleaning the feature
> > detect output. This is because O= and OUTPUT= are set to canonical
> > paths. For example in tools/perf/Makefile:
> >
> > FULL_O := $(shell cd $(PWD); readlink -f $(O) || echo $(O))
> >
> > This means that OUTPUT ends in a / and most usages prepend it to a file
> > without adding an extra /. This line that was changed adds an extra /
> > before the 'feature' folder but not to the end, resulting in a clean
> > command like this:
> >
> > rm -f /tmp/build//featuretest-all.bin ...
> >
> > After the change the clean command looks like this:
> >
> > rm -f /tmp/build/feature/test-all.bin ...
> >
> > Signed-off-by: James Clark <james.clark@arm.com>
>
> nice catch!
>
> Acked-by: Jiri Olsa <jolsa@redhat.com>
Thanks, applied and added:
Fixes: 762323eb39a257c3 ("perf build: Move feature cleanup under tools/build")
- Arnaldo
prev parent reply other threads:[~2021-09-01 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 13:07 [PATCH] tools build: Fix feature detect clean for out of source builds James Clark
2021-08-31 18:46 ` Jiri Olsa
2021-09-01 14:26 ` Arnaldo Carvalho de Melo [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=YS+NlBGl1xMqHlgC@kernel.org \
--to=acme@kernel.org \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@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).