From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
namhyung@kernel.org, Jiri Olsa <jolsa@redhat.com>,
Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH perf/core ] [BUGFIX] perf build-test: Add linux/export.h and lib/rbtree.c to MANIFEST
Date: Wed, 15 Jul 2015 15:07:18 +0900 [thread overview]
Message-ID: <20150715060718.10311.42010.stgit@localhost.localdomain> (raw)
Since linux/export.h and lib/rbtree.c are not listed in MANIFEST,
`make build-test` always fails as below (Note, to get these messages,
I've removed /dev/null redirect in tests/perf-targz-src-pkg);
----
CC util/hweight.o
../../lib/hweight.c:1:26: fatal error: linux/export.h:
No such file or directory
#include <linux/export.h>
^
compilation terminated.
make[3]: *** [util/hweight.o] Error 1
----
----
GEN common-cmds.h
make[1]: *** No rule to make target `../../lib/rbtree.c',
needed by `python/perf.so'. Stop.
make[1]: *** Waiting for unfinished jobs....
----
Signed-off-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
---
tools/perf/MANIFEST | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/perf/MANIFEST b/tools/perf/MANIFEST
index 09dc0aa..adce9de 100644
--- a/tools/perf/MANIFEST
+++ b/tools/perf/MANIFEST
@@ -58,7 +58,9 @@ include/linux/list.h
include/linux/hash.h
include/linux/stringify.h
lib/hweight.c
+lib/rbtree.c
include/linux/swab.h
+include/linux/export.h
arch/*/include/asm/unistd*.h
arch/*/include/uapi/asm/unistd*.h
arch/*/include/uapi/asm/perf_regs.h
next reply other threads:[~2015-07-15 6:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 6:07 Masami Hiramatsu [this message]
2015-07-15 11:22 ` [PATCH perf/core ] [BUGFIX] perf build-test: Add linux/export.h and lib/rbtree.c to MANIFEST Arnaldo Carvalho de Melo
2015-07-15 13:51 ` Masami Hiramatsu
2015-07-15 14:11 ` 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=20150715060718.10311.42010.stgit@localhost.localdomain \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=acme@kernel.org \
--cc=jolsa@redhat.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 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.