public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Ingo Molnar <mingo@kernel.org>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	David Ahern <dsahern@gmail.com>,
	Namhyung Kim <namhyung@kernel.org>
Subject: [GIT PULL] tools/perf/build: Speed up the perf build system
Date: Fri, 11 Oct 2013 00:13:22 +0200	[thread overview]
Message-ID: <20131010221322.GA1067@krava.redhat.com> (raw)
In-Reply-To: <20131010200627.GK28369@ghostprotocols.net>

Arnaldo, David,
wrt to our IRC discussion..

attached patch fixies the static build David is using:
make O=/tmp/perf LDFLAGS=-static DEBUG=1 -j 4

I still got some warning though:
  LINK     /tmp/perf/perf
/tmp/perf/libperf.a(target.o): In function `perf_target__parse_uid':
/home/jolsa/kernel.org/linux-perf/tools/perf/util/target.c:72: warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/home/jolsa/kernel.org/linux-perf/tools/perf/util/target.c:84: warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/lib/gcc/x86_64-redhat-linux/4.7.2/../../../../lib64/libpthread.a(libpthread.o): In function `sem_open':
(.text+0x67f8): warning: the use of `mktemp' is dangerous, better use `mkstemp'

but I guess it's ok ;-) feel free to melt the
change into the original patch

This change is on top of the NO_DEMANGLE fix in:
  git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
  acme_test

jirka

diff --git a/tools/perf/config/Makefile b/tools/perf/config/Makefile
index 233dd36..9680424 100644
--- a/tools/perf/config/Makefile
+++ b/tools/perf/config/Makefile
@@ -504,7 +504,7 @@ else
   endif
 endif
 
-ifndef ($(filter -lbfd,$(EXTLIBS)),)
+ifneq ($(filter -lbfd,$(EXTLIBS)),)
   CFLAGS += -DHAVE_LIBBFD_SUPPORT
 endif

  reply	other threads:[~2013-10-10 22:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09  7:01 [GIT PULL] tools/perf/build: Speed up the perf build system Ingo Molnar
2013-10-09 14:38 ` Arnaldo Carvalho de Melo
2013-10-09 14:51   ` Ingo Molnar
2013-10-09 15:00     ` [PATCH] tools/perf/build: Fix non-existent build directory handling Ingo Molnar
2013-10-15  5:33       ` [tip:perf/core] " tip-bot for Ingo Molnar
2013-10-09 19:16     ` [GIT PULL] tools/perf/build: Speed up the perf build system Arnaldo Carvalho de Melo
2013-10-09 19:38       ` Arnaldo Carvalho de Melo
2013-10-10  5:42       ` [PATCH] tools/perf/build: Fix redirection printouts Ingo Molnar
2013-10-15  5:31         ` [tip:perf/core] perf tools: " tip-bot for Ingo Molnar
2013-10-10  6:10       ` [PATCH] tools/perf/build: Pass through DEBUG parameter Ingo Molnar
2013-10-10 19:26     ` [GIT PULL] tools/perf/build: Speed up the perf build system Arnaldo Carvalho de Melo
2013-10-10 19:50       ` Arnaldo Carvalho de Melo
2013-10-10 20:06         ` Arnaldo Carvalho de Melo
2013-10-10 22:13           ` Jiri Olsa [this message]
2013-10-10 22:29             ` David Ahern

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=20131010221322.GA1067@krava.redhat.com \
    --to=jolsa@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=dsahern@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.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