[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPQBkrOtJkn_M+7hBJC-amxZ7SHQ+E_7gf2XiVzxCBbeEkxapw@mail.gmail.com>
Date: Mon, 27 May 2013 16:15:00 +0800
From: Runzhen Wang <icycoder@...il.com>
To: acme@...hat.com
Cc: mingo@...nel.org, linux-kernel@...r.kernel.org,
David Ahern <dsahern@...il.com>
Subject: Re: [PATCH] perf tools: fix a wrong header file path in util/unwind.c
Sorry, I made a mistake.....
There is no bug, please ignore my patch.
Sorry again. I will be careful next time.
On Mon, May 27, 2013 at 3:54 PM, Runzhen Wang <icycoder@...il.com> wrote:
> 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@...ux.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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists