[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160831072128.GB4740@krava>
Date: Wed, 31 Aug 2016 09:21:28 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Alexey Brodkin <Alexey.Brodkin@...opsys.com>
Cc: linux-kernel@...r.kernel.org, linux-snps-arc@...ts.infradead.org,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Vineet Gupta <Vineet.Gupta1@...opsys.com>,
Wang Nan <wangnan0@...wei.com>, Jiri Olsa <jolsa@...nel.org>,
He Kuang <hekuang@...wei.com>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Namhyung Kim <namhyung@...nel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Zefan Li <lizefan@...wei.com>, pi3orama@....com
Subject: Re: [PATCH] perf tools: Fix static building
On Mon, Aug 22, 2016 at 08:33:42PM +0300, Alexey Brodkin wrote:
> With commit e3d09ec8126f ("tools lib traceevent: Export dynamic symbols
> used by traceevent plugins") we started to add "--dynamic-list" in
> LDFLAGS. One side-effect of that was inability to build really
> statically-linked perf.
IIRC --dynamic-list forces perf to exports some symbols to
be used by plugins.. don't see this breaking static build
also it's working properly for me:
[jolsa@...va perf]$ make LDFLAGS=-static
...
[jolsa@...va perf]$ ldd ./perf
not a dynamic executable
unless I miss what you mean by 'really statically-linked' ;-)
Maybe different features enabled/build environment could you
please send the .config-detected along with the build error?
thanks,
jirka
Powered by blists - more mailing lists