On Thu, Jan 15, 2015 at 09:01:05AM -0700, David Ahern wrote: > On 1/15/15 5:55 AM, Jiri Olsa wrote: > > >diff --git a/tools/perf/Makefile.perf b/tools/perf/Makefile.perf > >index 1f71a32aea78..dd49b40e203b 100644 > >--- a/tools/perf/Makefile.perf > >+++ b/tools/perf/Makefile.perf > >@@ -84,6 +84,10 @@ ifneq ($(OUTPUT),) > > #$(info Determined 'OUTPUT' to be $(OUTPUT)) > > endif > > > >+# Do not use make's built-in rules and variables > >+# (this increases performance and avoids hard-to-debug behaviour); > >+MAKEFLAGS += -rR > >+ > > $(OUTPUT)PERF-VERSION-FILE: ../../.git/HEAD > > @$(SHELL_PATH) util/PERF-VERSION-GEN $(OUTPUT) > > @touch $(OUTPUT)PERF-VERSION-FILE > > Does this depend on any prior patch? Was not obvious to me. Adding just this > patch to a fresh build and it blows up. > > $ vi Makefile.perf > - add line above > $ mkdir /tmp/junk2 > $ make O=/tmp/junk2 > ... > CC /tmp/junk2/fs/debugfs.o > CC /tmp/junk2/fs/fs.o > CC /tmp/junk2/fd/array.o > /bin/sh: .event-parse.d: command not found > /bin/sh: .trace-seq.d: command not found > /bin/sh: .event-plugin.d: command not found > make[3]: *** [.event-parse.d] Error 127 > make[3]: *** Waiting for unfinished jobs.... > ... > > This is on a Fedora 16 host.
oops, I've cut it out of the framework changes to make it simpler, but looks like traceevent library depends on builtin rules, I'll check.. thanks, jirka -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/