[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8deeb70b-6fe8-32c5-9f6f-65b2d6bd70eb@synopsys.com>
Date: Thu, 1 Sep 2016 11:28:29 -0700
From: Vineet Gupta <Vineet.Gupta1@...opsys.com>
To: Jiri Olsa <jolsa@...hat.com>,
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 08/31/2016 12:21 AM, Jiri Olsa wrote:
> 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' ;-)
Right - so I tried this as well and indeed I can confirm that it builds for me as
static. Atleast the build system doesn;t need changing as -sattic being propagated
to fianl link cmd.
There seems to be some weirdness with ARC tools: file reports
| ELF 32-bit LSB executable, *unknown arch 0xc3* version 1 (SYSV),
| dynamically linked, interpreter *empty*, for GNU/Linux 3.9.0, not stripped
That is clearly wrong !
And the static binary as expected doesn't seem to run on target - exits with -EACCESS.
-Vineet
Powered by blists - more mailing lists