From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Jiri Olsa <jolsa@kernel.org>, Wang Nan <wangnan0@huawei.com>,
lkml <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>, Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] tools build: Use fixdep with OUTPUT path prefix
Date: Thu, 26 Nov 2015 16:31:06 -0300 [thread overview]
Message-ID: <20151126193106.GG28162@kernel.org> (raw)
In-Reply-To: <20151126185055.GC19410@krava.brq.redhat.com>
Em Thu, Nov 26, 2015 at 07:50:55PM +0100, Jiri Olsa escreveu:
> On Thu, Nov 26, 2015 at 07:12:04PM +0100, Jiri Olsa wrote:
> > On Thu, Nov 26, 2015 at 01:31:30PM -0300, Arnaldo Carvalho de Melo wrote:
> > > Em Thu, Nov 26, 2015 at 02:54:03PM +0100, Jiri Olsa escreveu:
> > > > Using FEATURE-INCLUDE in bpf subproject in case bpf is built
> > > > via perf. Keep the current features detection for other cases.
> > > >
> > > > Cc: Wang Nan <wangnan0@huawei.com>
> > > > Link: http://lkml.kernel.org/n/tip-utuczk899ckz6qtggqvhm7yu@git.kernel.org
> > > > Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> > >
> > > Clashes with:
> > >
> > > d8ad6a15cc3a ("tools lib bpf: Don't do a feature check when cleaning")
> > >
> > > That has, at that point:
> > >
> > > +check_feat := 1
> > > +NON_CHECK_FEAT_TARGETS := clean TAGS tags cscope help
> > > +ifdef MAKECMDGOALS
> > > +ifeq ($(filter-out $(NON_CHECK_FEAT_TARGETS),$(MAKECMDGOALS)),)
> > > + check_feat := 0
> > > +endif
> > > +endif
> > > +
> > > +ifeq ($(check_feat),1)
> > > include $(srctree)/tools/build/Makefile.feature
> > > +endif
> > >
> > > On a related note:
> > >
> > > [acme@zoo linux]$ make O=/tmp/build/perf -C tools/perf
> > > make: Entering directory '/home/git/linux/tools/perf'
> > > BUILD: Doing 'make -j4' parallel build
> > > make[2]: Nothing to be done for 'fixdep'.
> > > make: Leaving directory '/home/git/linux/tools/perf'
> > >
> > > Can we get away with that "make[2]: Nothing to be done for 'fixdep'."
> > > line?
> >
> > I'll check on that
>
> good we don't supress all make's output, sometimes it
> finds a bug ;-) please check with attached patch..
>
> thanks,
> jirka
Clashes with:
commit 5725dd8fa888b4dcdff58241f9d3d3ac42a048e2
Author: Wang Nan <wangnan0@huawei.com>
Date: Tue Nov 24 13:36:06 2015 +0000
tools build: Clean CFLAGS and LDFLAGS for fixdep
And this should even be already in tip, let me see, yes:
https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?h=perf/core&id=5725dd8fa888b4dcdff58241f9d3d3ac42a048e2
I'm fixing this up, as this one is easy.
- Arnaldo
>
> ---
> Adding OUTPUT path prefix for fixdep target
> so we use it properly in out of tree builds.
>
> If the fixdep already existed in the tree, the out of
> tree build would see it already exist and did not build
> the out of tree version, as reported by Arnaldo:
>
> [acme@zoo linux]$ make O=/tmp/build/perf -C tools/perf
> make: Entering directory '/home/git/linux/tools/perf'
> BUILD: Doing 'make -j4' parallel build
> make[2]: Nothing to be done for 'fixdep'.
> make: Leaving directory '/home/git/linux/tools/perf'
>
> Reported-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> Link: http://lkml.kernel.org/n/tip-hsrwmiogt9menjsg7uaxqvq2@git.kernel.org
> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> ---
> tools/build/Makefile | 2 +-
> tools/build/Makefile.include | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/build/Makefile b/tools/build/Makefile
> index a93036272d43..0d5a0e3a8fa9 100644
> --- a/tools/build/Makefile
> +++ b/tools/build/Makefile
> @@ -25,7 +25,7 @@ export Q srctree CC LD
> MAKEFLAGS := --no-print-directory
> build := -f $(srctree)/tools/build/Makefile.build dir=. obj
>
> -all: fixdep
> +all: $(OUTPUT)fixdep
>
> clean:
> $(call QUIET_CLEAN, fixdep)
> diff --git a/tools/build/Makefile.include b/tools/build/Makefile.include
> index 4e09ad617a60..6d5edd275bef 100644
> --- a/tools/build/Makefile.include
> +++ b/tools/build/Makefile.include
> @@ -4,7 +4,7 @@ ifdef CROSS_COMPILE
> fixdep:
> else
> fixdep:
> - $(Q)$(MAKE) -C $(srctree)/tools/build fixdep
> + $(Q)$(MAKE) -C $(srctree)/tools/build $(OUTPUT)fixdep
> endif
>
> .PHONY: fixdep
> --
> 2.4.3
next prev parent reply other threads:[~2015-11-26 19:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 13:54 [PATCH 1/3] tools build: Introduce features dump include makefile Jiri Olsa
2015-11-26 13:54 ` [PATCH 2/3] perf build: Use FEATURE-INCLUDE in bpf subproject Jiri Olsa
2015-11-26 16:31 ` Arnaldo Carvalho de Melo
2015-11-26 18:11 ` Jiri Olsa
2015-11-26 18:12 ` Jiri Olsa
2015-11-26 18:50 ` [PATCH] tools build: Use fixdep with OUTPUT path prefix Jiri Olsa
2015-11-26 19:31 ` Arnaldo Carvalho de Melo [this message]
2015-11-27 7:45 ` [tip:perf/core] " tip-bot for Jiri Olsa
2015-11-26 13:54 ` [PATCH 3/3] perf build: Fix traceevent plugins build race Jiri Olsa
2015-11-26 16:36 ` Arnaldo Carvalho de Melo
2015-11-27 7:44 ` [tip:perf/core] " tip-bot for Jiri Olsa
2015-11-26 16:23 ` [PATCH 1/3] tools build: Introduce features dump include makefile Arnaldo Carvalho de Melo
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=20151126193106.GG28162@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=wangnan0@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.