From: Jiri Olsa <jolsa@redhat.com>
To: Kyeongmin Cho <korea.drzix@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-kernel@vger.kernel.org, Wang Nan <wangnan0@huawei.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH 2/2] perf report: Add gcc option '-rdynamic' to define symbol callchain_param
Date: Sun, 1 May 2016 17:44:52 +0200 [thread overview]
Message-ID: <20160501154452.GA30164@krava> (raw)
In-Reply-To: <CAMD-KS8brrEo=tDKVr4piwFtgeueH1W=831rRo4Km5TGBjCmSg@mail.gmail.com>
On Thu, Apr 28, 2016 at 11:49:06PM +0900, Kyeongmin Cho wrote:
> Hi,
>
> Althogh applying my previous patch, it still prints
>
> $ ./perf report --gtk
> GTK browser requested but could not find libperf-gtk.so
>
> When printing dlerror() in setup_gtk_browser(),
>
> $ ./perf report --gtk
> /home/drzix/lib64/libperf-gtk.so: undefined symbol: callchain_param
> GTK browser requested but could not find libperf-gtk.so
>
> After applying this patch, compiling rdynamically to make
> libperf-gtk.so find out the symbol, it works.
hum, I'm running that with:
LD_LIBRARY_PATH=$PWD ./perf report --gtk
jirka
next prev parent reply other threads:[~2016-05-01 15:44 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 ` [PATCH 2/2] perf report: Add gcc option '-rdynamic' to define symbol callchain_param Kyeongmin Cho
2016-04-28 14:12 ` Jiri Olsa
2016-04-28 14:49 ` Kyeongmin Cho
2016-05-01 15:44 ` Jiri Olsa [this message]
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=20160501154452.GA30164@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=korea.drzix@gmail.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 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.