linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Peter Foley <pefoley2@pefoley.com>,
	LKML <linux-kernel@vger.kernel.org>,
	wangnan0@huawei.com
Subject: Re: [PATCHv3] tools build: Make fixdep parsing wait for last target
Date: Fri, 2 Dec 2016 09:49:10 +0100	[thread overview]
Message-ID: <20161202084910.GA21304@krava> (raw)
In-Reply-To: <20161201185323.GB4953@redhat.com>

On Thu, Dec 01, 2016 at 04:53:23PM -0200, Arnaldo Carvalho de Melo wrote:

SNIP

> [acme@jouet linux]$ m
> make: Entering directory '/home/acme/git/linux/tools/perf'
>   BUILD:   Doing 'make -j4' parallel build
>   CC       /tmp/build/perf/jvmti/libjvmti.o
>   CC       /tmp/build/perf/jvmti/jvmti_agent.o
>   HOSTCC   /tmp/build/perf/pmu-events/json.o
>   HOSTCC   /tmp/build/perf/fixdep.o
>   HOSTCC   /tmp/build/perf/pmu-events/jsmn.o
>   HOSTLD   /tmp/build/perf/fixdep-in.o
>   LINK     /tmp/build/perf/fixdep
> /bin/sh: /tmp/build/perf//fixdep: Permission denied
> /home/acme/git/linux/tools/build/Makefile.build:91: recipe for target '/tmp/build/perf/pmu-events/jsmn.o' failed

I think this is unrelated.. I think we're missing jevents fixdep dependency

I'll test patch below and send it separately

jirka

---
diff --git a/tools/perf/Makefile.perf b/tools/perf/Makefile.perf
index 3cb1df43ad3e..5d968af132e2 100644
--- a/tools/perf/Makefile.perf
+++ b/tools/perf/Makefile.perf
@@ -465,7 +465,7 @@ $(PERF_IN): prepare FORCE
 	|| echo "Warning: tools/include/uapi/linux/mman.h differs from kernel" >&2 )) || true
 	$(Q)$(MAKE) $(build)=perf
 
-$(JEVENTS_IN): FORCE
+$(JEVENTS_IN): fixdep FORCE
 	$(Q)$(MAKE) -f $(srctree)/tools/build/Makefile.build dir=pmu-events obj=jevents
 
 $(JEVENTS): $(JEVENTS_IN)

  reply	other threads:[~2016-12-02  8:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-26 22:20 [PATCH] Fix objtool with clang Peter Foley
2016-11-27 16:14 ` Jiri Olsa
2016-11-28  2:43   ` [PATCH v2] " Peter Foley
2016-11-28 11:39     ` Jiri Olsa
2016-11-28 15:00       ` Arnaldo Carvalho de Melo
2016-11-28 15:25         ` Peter Foley
2016-11-28 16:58           ` Jiri Olsa
2016-11-28 19:40             ` Arnaldo Carvalho de Melo
2016-11-28 20:08               ` Jiri Olsa
2016-11-29  9:32               ` Jiri Olsa
2016-11-29  9:58                 ` Jiri Olsa
2016-11-29 14:28               ` Jiri Olsa
2016-11-29 14:33                 ` Arnaldo Carvalho de Melo
2016-11-29 14:39                   ` Jiri Olsa
2016-11-29 14:49                     ` Arnaldo Carvalho de Melo
2016-11-29 15:24                       ` Jiri Olsa
2016-12-01 13:00                       ` [PATCHv3] tools build: Make fixdep parsing wait for last target Jiri Olsa
2016-12-01 17:48                         ` Peter Foley
2016-12-01 18:53                           ` Arnaldo Carvalho de Melo
2016-12-02  8:49                             ` Jiri Olsa [this message]
2016-12-02  9:15                             ` Jiri Olsa
2016-12-02 15:10                               ` Arnaldo Carvalho de Melo
2016-12-06  8:20                         ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-11-28 19:35           ` [PATCH v2] Fix objtool with clang Arnaldo Carvalho de Melo
2016-12-06  8:20     ` [tip:perf/core] tools build: Fix objtool build " tip-bot for Peter Foley

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=20161202084910.GA21304@krava \
    --to=jolsa@redhat.com \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pefoley2@pefoley.com \
    --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 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).