mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	linux-kernel@vger.kernel.org, Namhyung Kim <namhyung@gmail.com>
Subject: Re: [RFC/BUG] perf tools: static build fails
Date: Wed, 29 Jul 2015 10:30:34 +0200	[thread overview]
Message-ID: <20150729083034.GA31712@krava.brq.redhat.com> (raw)
In-Reply-To: <20150728212138.GF575@kernel.org>

On Tue, Jul 28, 2015 at 06:21:38PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Wed, Jul 29, 2015 at 12:14:41AM +0300, Adrian Hunter escreveu:
> > On 28/07/2015 7:11 p.m., Arnaldo Carvalho de Melo wrote:
> > >Em Tue, Jul 28, 2015 at 05:13:47PM +0200, Jiri Olsa escreveu:
> 
> > >>it's failing on perf-read-vdso32 tool..  attached patch fixes that
> > >>for me
> 
> > >To build it statically:
> 
> > >   make -C tools/perf O=/tmp/build/perf LDFLAGS=-static install-bin
> 
> > >Adrian, I wonder if building just these utilities non-statically when we
> > >ask for a static build of the main tool is ok, is it?
>  
> > Not really.
>  
> > Static build works for me, including building perf-read-vdso32 statically,
> > so I am not sure what the problem is?

oops, it was the 32bit glibc-static pkg missing.. I'm good now ;-)

> 
> The static build stops for me way before getting to these utilities, so
> I don't know, I fixed an unrelated problem, but Jiri is the one having
> trouble in this one, Jiri, can you post the output of the build when it
> fails?

[jolsa@krava perf]$ make LDFLAGS=-static JOBS=1

SNIP

  GEN      libtraceevent-dynamic-list
  LINK     perf
/home/jolsa/kernel/linux-perf/tools/lib/traceevent/libtraceevent.a(libtraceevent-in.o): In function `load_plugin':
/home/jolsa/kernel/linux-perf/tools/lib/traceevent/event-plugin.c:304: warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
libperf.a(libperf-in.o): In function `target__parse_uid':
/home/jolsa/kernel/linux-perf/tools/perf/util/target.c:79: warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/home/jolsa/kernel/linux-perf/tools/perf/util/target.c:91: warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
  CC       perf-read-vdso32
/bin/ld: cannot find -lc
collect2: error: ld returned 1 exit status
Makefile.perf:373: recipe for target 'perf-read-vdso32' failed
make[1]: *** [perf-read-vdso32] Error 1
Makefile:68: recipe for target 'all' failed
make: *** [all] Error 2


jirka

      reply	other threads:[~2015-07-29  8:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28 15:13 Jiri Olsa
2015-07-28 16:11 ` Arnaldo Carvalho de Melo
2015-07-28 21:14   ` Adrian Hunter
2015-07-28 21:21     ` Arnaldo Carvalho de Melo
2015-07-29  8:30       ` Jiri Olsa [this message]

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=20150729083034.GA31712@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@gmail.com \
    --cc=peterz@infradead.org \
    /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

Powered by JetHome