From: Runzhen Wang <icycoder@gmail.com>
To: acme@redhat.com
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org,
dsahern@gmail.com, Runzhen Wang <icycoder@gmail.com>,
Runzhen Wang <runzhen@linux.vnet.ibm.com>
Subject: [PATCH] perf tools: fix a wrong header file path in util/unwind.c
Date: Mon, 27 May 2013 15:54:26 +0800 [thread overview]
Message-ID: <1369641266-16913-1-git-send-email-icycoder@gmail.com> (raw)
For the latest perf core tree:
(git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git),
in util/unwind.c line 29 includes "perf_regs.h". That means compiler
will search for this header file in current directory, so, gcc will
puts the following error messages:
util/unwind.c: In function ‘access_mem’:
util/unwind.c:400:50: error: ‘PERF_REG_SP’ undeclared (first use in this
function)
util/unwind.c:400:50: note: each undeclared identifier is reported only
once for each function it appears in
util/unwind.c: In function ‘unwind__get_entries’:
util/unwind.c:562:41: error: ‘PERF_REG_IP’ undeclared (first use in this
function)
Changing #include "perf_regs.h" to #include <perf_regs.h> will fix the
error.
Signed-off-by: Runzhen Wang <runzhen@linux.vnet.ibm.com>
---
tools/perf/util/unwind.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/util/unwind.c b/tools/perf/util/unwind.c
index 958723b..50e14f7 100644
--- a/tools/perf/util/unwind.c
+++ b/tools/perf/util/unwind.c
@@ -26,7 +26,7 @@
#include <libunwind-ptrace.h>
#include "thread.h"
#include "session.h"
-#include "perf_regs.h"
+#include <perf_regs.h>
#include "unwind.h"
#include "util.h"
--
1.7.9.5
next reply other threads:[~2013-05-27 7:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 7:54 Runzhen Wang [this message]
2013-05-27 8:15 ` [PATCH] perf tools: fix a wrong header file path in util/unwind.c Runzhen Wang
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=1369641266-16913-1-git-send-email-icycoder@gmail.com \
--to=icycoder@gmail.com \
--cc=acme@redhat.com \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=runzhen@linux.vnet.ibm.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.