From: Kyeongmin Cho <korea.drzix@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@redhat.com>,
Wang Nan <wangnan0@huawei.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Kyeongmin Cho <korea.drzix@gmail.com>
Subject: [PATCH 2/2] perf report: Add gcc option '-rdynamic' to define symbol callchain_param
Date: Thu, 28 Apr 2016 22:00:01 +0900 [thread overview]
Message-ID: <1461848401-32125-2-git-send-email-korea.drzix@gmail.com> (raw)
In-Reply-To: <1461848401-32125-1-git-send-email-korea.drzix@gmail.com>
As libperf-gtk.so cannot find out undefined symbol 'callchain_param',
'-rdynamic' option is needed to add the symbol to the dynamic symbol
table.
Signed-off-by: Kyeongmin Cho <korea.drzix@gmail.com>
---
tools/perf/Makefile.perf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/Makefile.perf b/tools/perf/Makefile.perf
index 000ea21..a3f8b39 100644
--- a/tools/perf/Makefile.perf
+++ b/tools/perf/Makefile.perf
@@ -344,7 +344,7 @@ $(PERF_IN): prepare FORCE
$(Q)$(MAKE) $(build)=perf
$(OUTPUT)perf: $(PERFLIBS) $(PERF_IN) $(LIBTRACEEVENT_DYNAMIC_LIST)
- $(QUIET_LINK)$(CC) $(CFLAGS) $(LDFLAGS) $(LIBTRACEEVENT_DYNAMIC_LIST_LDFLAGS) \
+ $(QUIET_LINK)$(CC) $(CFLAGS) $(LDFLAGS) -rdynamic $(LIBTRACEEVENT_DYNAMIC_LIST_LDFLAGS) \
$(PERF_IN) $(LIBS) -o $@
$(GTK_IN): fixdep FORCE
--
2.5.5
next prev parent reply other threads:[~2016-04-28 13:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 13:00 [PATCH 1/2] perf report: Find lib path correctly for gtk option Kyeongmin Cho
2016-04-28 13:00 ` Kyeongmin Cho [this message]
2016-04-28 14:12 ` [PATCH 2/2] perf report: Add gcc option '-rdynamic' to define symbol callchain_param Jiri Olsa
2016-04-28 14:49 ` Kyeongmin Cho
2016-05-01 15:44 ` Jiri Olsa
2016-04-28 15:26 ` Arnaldo Carvalho de Melo
2016-04-28 14:07 ` [PATCH 1/2] perf report: Find lib path correctly for gtk option Jiri Olsa
2016-04-28 14:35 ` drzix
2016-04-29 11:50 ` Namhyung Kim
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=1461848401-32125-2-git-send-email-korea.drzix@gmail.com \
--to=korea.drzix@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=wangnan0@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®