From: dsahern@gmail.com (David Ahern)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] perf: parse the .debug_frame section in case .eh_frame is not present
Date: Tue, 10 Sep 2013 12:14:30 -0700 [thread overview]
Message-ID: <522F6F96.8030803@gmail.com> (raw)
In-Reply-To: <1378720815-23964-4-git-send-email-jean.pihet@linaro.org>
On 9/9/13 3:00 AM, Jean Pihet wrote:
> diff --git a/tools/perf/config/Makefile b/tools/perf/config/Makefile
> index 7014373..54532b8 100644
> --- a/tools/perf/config/Makefile
> +++ b/tools/perf/config/Makefile
> @@ -222,7 +222,7 @@ endif
>
> FLAGS_UNWIND=$(LIBUNWIND_CFLAGS) $(CFLAGS) $(LIBUNWIND_LDFLAGS) $(LDFLAGS) $(EXTLIBS) $(LIBUNWIND_LIBS)
> ifneq ($(call try-cc,$(SOURCE_LIBUNWIND),$(FLAGS_UNWIND),libunwind),y)
> - msg := $(warning No libunwind found, disabling post unwind support. Please install libunwind-dev[el] >= 0.99);
> + msg := $(warning No libunwind found, disabling post unwind support. Please install libunwind-dev[el] >= 1.1);
> NO_LIBUNWIND := 1
> endif # Libunwind support
> endif # NO_LIBUNWIND
Is the 1.1 version required for x86 too?
David
next prev parent reply other threads:[~2013-09-10 19:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 10:00 [PATCH 0/3] perf: parse the dwarf backtrace info from .debug_frame section Jean Pihet
2013-09-09 10:00 ` [PATCH 1/3] ARM: perf: add support for perf registers API Jean Pihet
2013-09-09 10:00 ` [PATCH 2/3] ARM: perf: wire up perf_regs and unwind support for ARM Jean Pihet
2013-09-09 10:00 ` [PATCH 3/3] perf: parse the .debug_frame section in case .eh_frame is not present Jean Pihet
2013-09-10 19:14 ` David Ahern [this message]
2013-09-10 19:38 ` Jean Pihet
2013-09-12 12:38 ` Jiri Olsa
2013-09-10 7:29 ` [PATCH 0/3] perf: parse the dwarf backtrace info from .debug_frame section Jean Pihet
2013-09-12 12:07 ` Jean Pihet
2013-09-12 12:19 ` Peter Zijlstra
2013-09-12 12:28 ` Will Deacon
-- strict thread matches above, loose matches on Subject: below --
2013-09-04 18:04 Jean Pihet
2013-09-04 18:04 ` [PATCH 3/3] perf: parse the .debug_frame section in case .eh_frame is not present Jean Pihet
2013-09-05 12:45 ` Will Deacon
2013-09-05 13:05 ` Jean Pihet
2013-09-05 13:17 ` Ard Biesheuvel
2013-09-05 13:19 ` Will Deacon
2013-09-05 13:33 ` Jean Pihet
2013-09-05 15:29 ` Jean Pihet
2013-09-05 15:45 ` Ard Biesheuvel
2013-09-05 13:10 ` Ard Biesheuvel
2013-09-05 16:30 ` Jiri Olsa
2013-09-05 16:49 ` Jean Pihet
2013-09-06 10:17 ` Jiri Olsa
2013-09-06 9:31 ` Jean Pihet
2013-09-06 10:17 ` Jiri Olsa
2013-09-06 14:10 ` Jean Pihet
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=522F6F96.8030803@gmail.com \
--to=dsahern@gmail.com \
--cc=linux-arm-kernel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).