Re: [PATCH] perf: Ensure symbols for plugins are exported

2015-04-22 Thread Mathias Krause
On 18 April 2015 at 17:46, Jiri Olsa wrote: > On Fri, Apr 17, 2015 at 11:01:07PM +0200, Mathias Krause wrote: >> On 17 April 2015 at 17:34, Jiri Olsa wrote: >> > On Sun, Apr 12, 2015 at 06:00:51PM +0200, Mathias Krause wrote: >> >> When building perf with perl or python support it implicitly gets

Re: [PATCH] perf: Ensure symbols for plugins are exported

2015-04-18 Thread Jiri Olsa
On Fri, Apr 17, 2015 at 11:01:07PM +0200, Mathias Krause wrote: > On 17 April 2015 at 17:34, Jiri Olsa wrote: > > On Sun, Apr 12, 2015 at 06:00:51PM +0200, Mathias Krause wrote: > >> When building perf with perl or python support it implicitly gets linked > >> with the -export-dynamic linker optio

Re: [PATCH] perf: Ensure symbols for plugins are exported

2015-04-17 Thread Mathias Krause
On 17 April 2015 at 17:34, Jiri Olsa wrote: > On Sun, Apr 12, 2015 at 06:00:51PM +0200, Mathias Krause wrote: >> When building perf with perl or python support it implicitly gets linked >> with the -export-dynamic linker option through the additional linker >> flags, namely with -Wl,-E via perl or

Re: [PATCH] perf: Ensure symbols for plugins are exported

2015-04-17 Thread Jiri Olsa
On Sun, Apr 12, 2015 at 06:00:51PM +0200, Mathias Krause wrote: > When building perf with perl or python support it implicitly gets linked > with the -export-dynamic linker option through the additional linker > flags, namely with -Wl,-E via perl or -Xlinker -export-dynamic via > python. That flag

[PATCH] perf: Ensure symbols for plugins are exported

2015-04-12 Thread Mathias Krause
When building perf with perl or python support it implicitly gets linked with the -export-dynamic linker option through the additional linker flags, namely with -Wl,-E via perl or -Xlinker -export-dynamic via python. That flag is essential for the traceevent plugin support so we shouldn't rely on a