From: Jiri Olsa <jolsa@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Namhyung Kim <namhyung@kernel.org>,
Mike Galbraith <efault@gmx.de>,
Stephane Eranian <eranian@google.com>,
David Ahern <dsahern@gmail.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH] perf tools: Fix tags target rebuilding
Date: Tue, 26 Nov 2013 12:50:43 +0100 [thread overview]
Message-ID: <20131126115043.GG1267@krava.brq.redhat.com> (raw)
In-Reply-To: <20131126113108.GE2410@gmail.com>
On Tue, Nov 26, 2013 at 12:31:08PM +0100, Ingo Molnar wrote:
>
> * Jiri Olsa <jolsa@redhat.com> wrote:
>
> > Once the tags file is generated it's never rebuilt
> > until it's removed by hand.
> >
> > The reason is that the Makefile does not treat tags
> > as a target but as a file to be rebuilt.
> >
> > Adding tags as PHONY target into the Makefile.
> >
> > Signed-off-by: Jiri Olsa <jolsa@redhat.com>
> > Cc: Ingo Molnar <mingo@kernel.org>
> > Cc: Frederic Weisbecker <fweisbec@gmail.com>
> > Cc: Peter Zijlstra <peterz@infradead.org>
> > Cc: Namhyung Kim <namhyung@kernel.org>
> > Cc: Mike Galbraith <efault@gmx.de>
> > Cc: Stephane Eranian <eranian@google.com>
> > Cc: David Ahern <dsahern@gmail.com>
> > Cc: Adrian Hunter <adrian.hunter@intel.com>
> > Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> > ---
> > tools/perf/Makefile | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/tools/perf/Makefile b/tools/perf/Makefile
> > index 4835618..95f5792 100644
> > --- a/tools/perf/Makefile
> > +++ b/tools/perf/Makefile
> > @@ -61,7 +61,7 @@ endef
> > #
> > # Needed if no target specified:
> > #
> > -all:
> > +all tags:
>
> Obviously the change invalidates the comment above.
ugh, haven't noticed that comment ;-)
>
> > $(print_msg)
> > $(make)
> >
> > @@ -77,3 +77,5 @@ clean:
> > %:
> > $(print_msg)
> > $(make)
> > +
> > +.PHONY: tags
>
> Note that there's also a TAGS file that uses etags - which probably
> needs similar treatment.
yes
>
> Also note that we have duplicate code for this in Makefile.perf
> already. Would it be possible to pass through this there and keep the
> main Makefile is just a thin, minimal wrapper that adds default
> parallelism, etc?
well, thats what I actually tried to do.. pass the
processing to the Makefile.perf otherwise it stops
in Makefile
I guess you want some generic way of doing that
jirka
next prev parent reply other threads:[~2013-11-26 11:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 11:21 Jiri Olsa
2013-11-26 11:31 ` Ingo Molnar
2013-11-26 11:50 ` Jiri Olsa [this message]
2013-11-26 12:00 ` Ingo Molnar
2013-11-26 12:54 ` [PATCHv2] perf tools: Fix tags/TAGS targets rebuilding Jiri Olsa
2013-11-26 16:13 ` Ingo Molnar
2013-11-26 23:16 ` Jiri Olsa
2013-11-27 11:31 ` Ingo Molnar
2013-11-27 19:40 ` Arnaldo Carvalho de Melo
2013-11-30 12:54 ` [tip:perf/core] " tip-bot for Jiri Olsa
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=20131126115043.GG1267@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--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
all inboxes | Powered by JetHome®