From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung.kim@lge.com>,
LKML <linux-kernel@vger.kernel.org>,
Pekka Enberg <penberg@kernel.org>,
Andi Kleen <andi@firstfloor.org>, Jiri Olsa <jolsa@redhat.com>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/3] perf tools: Separate out GTK codes to libperf-gtk.so
Date: Thu, 8 Aug 2013 12:21:16 -0300 [thread overview]
Message-ID: <20130808152116.GG6102@ghostprotocols.net> (raw)
In-Reply-To: <1375943650-2273-2-git-send-email-namhyung@kernel.org>
Em Thu, Aug 08, 2013 at 03:34:08PM +0900, Namhyung Kim escreveu:
> Separate out GTK codes to a shared object called libperf-gtk.so. This
> time only GTK codes are built with -fPIC and libperf remains as is.
[acme@sandy linux]$ cat /etc/fedora-release
Fedora release 18 (Spherical Cow)
[acme@sandy linux]$
Applying: perf tools: Separate out GTK codes to libperf-gtk.so
[perf/core c1ca5ea] perf tools: Separate out GTK codes to libperf-gtk.so
Author: Namhyung Kim <namhyung@kernel.org>
2 files changed, 38 insertions(+), 15 deletions(-)
[acme@sandy linux]$ make -j8 O=/tmp/build/perf -C tools/perf/ install-bin
CHK -fstack-protector-all
<SNIP>
CC /tmp/build/perf/scripts/perl/Perf-Trace-Util/Context.o
CC /tmp/build/perf/util/scripting-engines/trace-event-python.o
CC /tmp/build/perf/scripts/python/Perf-Trace-Util/Context.o
GEN perf-archive
GEN /tmp/build/perf/python/perf.so
CC /tmp/build/perf/perf.o
AR /tmp/build/perf/libperf.a
LINK /tmp/build/perf/perf
LINK /tmp/build/perf/libperf-gtk.so
/usr/bin/ld: /tmp/build/perf/ui/gtk/browser.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
/tmp/build/perf/ui/gtk/browser.o: could not read symbols: Bad value
collect2: error: ld returned 1 exit status
make: *** [/tmp/build/perf/libperf-gtk.so] Error 1
make: *** Waiting for unfinished jobs....
make: Leaving directory `/home/acme/git/linux/tools/perf'
[acme@sandy linux]$
And if I just do:
[acme@sandy linux]$ rm -rf /tmp/build/perf
[acme@sandy linux]$ mkdir /tmp/build/perf
[acme@sandy linux]$ make -j8 O=/tmp/build/perf -C tools/perf/ install-bin
CHK -fstack-protector-all
CHK -Wstack-protector
CHK -Wvolatile-register-var
CHK -D_FORTIFY_SOURCE=2
CHK bionic
CHK libelf
CHK libdw
CHK -DLIBELF_MMAP
CHK -DLIBELF_MMAP
CHK libunwind
CHK libaudit
CHK libslang
CHK gtk2
CHK -DHAVE_GTK_INFO_BAR
CHK perl
CHK python
CHK python version
CHK libbfd
CHK -DHAVE_STRLCPY
CHK -DHAVE_ON_EXIT
CHK -DBACKTRACE_SUPPORT
CHK libnuma
make: Entering directory `/home/acme/git/linux/tools/perf'
MKDIR /tmp/build/perf/arch/
MKDIR /tmp/build/perf/arch/x86/util/
MKDIR /tmp/build/perf/bench/
MKDIR /tmp/build/perf/scripts/perl/Perf-Trace-Util/
MKDIR /tmp/build/perf/scripts/python/Perf-Trace-Util/
MKDIR /tmp/build/perf/ui/
MKDIR /tmp/build/perf/ui/browsers/
MKDIR /tmp/build/perf/tests/
MKDIR /tmp/build/perf/ui/stdio/
MKDIR /tmp/build/perf/ui/tui/
MKDIR /tmp/build/perf/util/
MKDIR /tmp/build/perf/util/scripting-engines/
* new build flags or prefix
BISON /tmp/build/perf/util/pmu-bison.c
CC /tmp/build/perf/util/environment.o
<SNIP>
CC /tmp/build/perf/builtin-buildid-cache.o
Assembler messages:
Fatal error: can't create /tmp/build/perf/ui/gtk/setup.o: No such file or directory
make: *** [/tmp/build/perf/ui/gtk/setup.o] Error 1
make: *** Waiting for unfinished jobs....
Assembler messages:
Fatal error: can't create /tmp/build/perf/ui/gtk/util.o: No such file or directory
make: *** [/tmp/build/perf/ui/gtk/util.o] Error 1
Assembler messages:
Fatal error: can't create /tmp/build/perf/ui/gtk/progress.o: No such file or directory
make: *** [/tmp/build/perf/ui/gtk/progress.o] Error 1
Assembler messages:
Fatal error: can't create /tmp/build/perf/ui/gtk/browser.o: No such file or directory
make: *** [/tmp/build/perf/ui/gtk/browser.o] Error 1
Assembler messages:
Fatal error: can't create /tmp/build/perf/ui/gtk/helpline.o: No such file or directory
make: *** [/tmp/build/perf/ui/gtk/helpline.o] Error 1
Assembler messages:
Fatal error: can't create /tmp/build/perf/ui/gtk/annotate.o: No such file or directory
make: *** [/tmp/build/perf/ui/gtk/annotate.o] Error 1
Assembler messages:
Fatal error: can't create /tmp/build/perf/ui/gtk/hists.o: No such file or directory
make: *** [/tmp/build/perf/ui/gtk/hists.o] Error 1
make: Leaving directory `/home/acme/git/linux/tools/perf'
[acme@sandy linux]$
next prev parent reply other threads:[~2013-08-08 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 6:34 [PATCH/RFC 0/3] perf ui/gtk: Separate out GTK code to a shared object (v3) Namhyung Kim
2013-08-08 6:34 ` [PATCH 1/3] perf tools: Separate out GTK codes to libperf-gtk.so Namhyung Kim
2013-08-08 15:21 ` Arnaldo Carvalho de Melo [this message]
2013-08-09 6:17 ` Namhyung Kim
2013-08-08 6:34 ` [PATCH 2/3] perf tools: Setup GTK browser dynamically Namhyung Kim
2013-08-08 6:34 ` [PATCH 3/3] perf tools: Run dynamic loaded GTK browser Namhyung Kim
-- strict thread matches above, loose matches on Subject: below --
2013-08-09 6:28 [PATCH 0/3] perf ui/gtk: Separate out GTK code to a shared object (v4) Namhyung Kim
2013-08-09 6:28 ` [PATCH 1/3] perf tools: Separate out GTK codes to libperf-gtk.so Namhyung Kim
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=20130808152116.GG6102@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=penberg@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