Em Fri, Aug 21, 2015 at 10:08:06PM +0300, Adrian Hunter escreveu: > On 21/08/2015 10:05 p.m., Adrian Hunter wrote: > >On 21/08/2015 7:33 p.m., Arnaldo Carvalho de Melo wrote: > >> CC util/scripting-engines/trace-event-python.o > >> CC util/intel-pt-decoder/intel-pt-insn-decoder.o > >>util/intel-pt-decoder/intel-pt-insn-decoder.c:23:22: fatal error: > >>asm/insn.h: No such file or directory > >> #include <asm/insn.h> > >> ^ > >>compilation terminated. > > > >Here is what I found was needed > > > >0001-perf-tools-Fix-tarball-build-broken-by-pt-bts.patch > > > > > > From 8d36bfbc31c4a845b0a22b2dd4fcca86be7f0058 Mon Sep 17 00:00:00 2001 > >From: Adrian Hunter<[email protected]> > >Date: Fri, 21 Aug 2015 21:57:42 +0300 > >Subject: [PATCH] perf tools: Fix tarball build broken by pt/bts > > > >Fix some include paths and add missing inat_types.h. > > > >Signed-off-by: Adrian Hunter<[email protected]> > >--- > > tools/perf/tests/perf-targz-src-pkg | 2 +- > > tools/perf/util/intel-pt-decoder/inat.c | 2 +- > > tools/perf/util/intel-pt-decoder/inat.h | 2 +- > > tools/perf/util/intel-pt-decoder/inat_types.h | 29 > > ++++++++++++++++++++++ > > tools/perf/util/intel-pt-decoder/insn.c | 4 +-- > > tools/perf/util/intel-pt-decoder/insn.h | 2 +- > > .../util/intel-pt-decoder/intel-pt-insn-decoder.c | 2 +- > > 7 files changed, 36 insertions(+), 7 deletions(-) > > create mode 100644 tools/perf/util/intel-pt-decoder/inat_types.h > > > >diff --git a/tools/perf/tests/perf-targz-src-pkg > >b/tools/perf/tests/perf-targz-src-pkg > >index 238aa39..261a912 100755 > >--- a/tools/perf/tests/perf-targz-src-pkg > >+++ b/tools/perf/tests/perf-targz-src-pkg > >@@ -17,5 +17,5 @@ rm -f ${TARBALL} > > cd - > /dev/null > > make -C $TMP_DEST/perf*/tools/perf > /dev/null 2>&1 > > RC=$? > >-rm -rf ${TMP_DEST} > >+#rm -rf ${TMP_DEST} > > Err, not that bit though.
I noticed that, removing, but that needs to be echoed in case of failure, deleted otherwise :) - Arnaldo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
