From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jeremie Galarneau <jgalar@efficios.com>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Tom Zanussi <tzanussi@gmail.com>
Subject: Re: [PATCH 1/8] perf tools: Add feature check for libbabeltrace
Date: Tue, 9 Dec 2014 11:14:16 +0100 [thread overview]
Message-ID: <20141209101416.GB2516@krava.brq.redhat.com> (raw)
In-Reply-To: <CAM9d7cixHgGqiLu0c8zrbEU6aLNdvhwC0vne4zcd8OZjQkCV1Q@mail.gmail.com>
On Mon, Dec 08, 2014 at 05:07:23PM +0900, Namhyung Kim wrote:
> Hi Jiri,
>
> On Thu, Dec 4, 2014 at 1:23 AM, Jiri Olsa <jolsa@kernel.org> wrote:
> > +ifndef NO_LIBBABELTRACE
> > + # for linking with debug library, run like:
> > + # make DEBUG=1 LIBBABELTRACE_DIR=/opt/libdw/
>
> s/libdw/libbabeltrace/
ouch.. copy&paste crap ;-)
>
>
> > + ifdef LIBBABELTRACE_DIR
> > + LIBBABELTRACE_CFLAGS := -I$(LIBBABELTRACE_DIR)/include
> > + LIBBABELTRACE_LDFLAGS := -L$(LIBBABELTRACE_DIR)/lib
> > + endif
> > + FEATURE_CHECK_CFLAGS-libbabeltrace := $(LIBBABELTRACE_CFLAGS)
> > + FEATURE_CHECK_LDFLAGS-libbabeltrace := $(LIBBABELTRACE_LDFLAGS) -lbabeltrace-ctf
> > +endif
> > +
> > # include ARCH specific config
> > -include $(src-perf)/arch/$(ARCH)/Makefile
> >
> > @@ -201,6 +212,7 @@ CORE_FEATURE_TESTS = \
> > stackprotector-all \
> > timerfd \
> > libdw-dwarf-unwind \
> > + libbabeltrace \
> > zlib
> >
> > LIB_FEATURE_TESTS = \
> > @@ -216,6 +228,7 @@ LIB_FEATURE_TESTS = \
> > libslang \
> > libunwind \
> > libdw-dwarf-unwind \
> > + libbabeltrace \
> > zlib
> >
> > VF_FEATURE_TESTS = \
> > @@ -661,6 +674,17 @@ else
> > NO_PERF_READ_VDSOX32 := 1
> > endif
> >
> > +ifndef NO_LIBBABELTRACE
> > + ifeq ($(feature-libbabeltrace), 0)
> > + msg := $(warning No libbabeltrace found, disables 'perf data' CTF format support, please install libbabeltrace-devel/libbabeltrace-dev);
>
> It seems that Ubuntu has libbabeltrace-ctf-dev package.
ok
thanks,
jirka
next prev parent reply other threads:[~2014-12-09 10:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 16:23 [PATCH 0/8] perf tools: Add perf data CTF conversion Jiri Olsa
2014-12-03 16:23 ` [PATCH 1/8] perf tools: Add feature check for libbabeltrace Jiri Olsa
2014-12-08 8:07 ` Namhyung Kim
2014-12-09 10:14 ` Jiri Olsa [this message]
2014-12-03 16:23 ` [PATCH 2/8] perf tools: Add new perf data command Jiri Olsa
2014-12-03 16:23 ` [PATCH 3/8] perf data: Add perf data to CTF conversion support Jiri Olsa
2014-12-08 8:13 ` Namhyung Kim
2014-12-09 10:16 ` Jiri Olsa
2014-12-03 16:23 ` [PATCH 4/8] perf data: Add a 'perf' prefix to the generic fields Jiri Olsa
2014-12-03 16:23 ` [PATCH 5/8] perf data: Add tracepoint events fields CTF conversion support Jiri Olsa
2014-12-03 16:24 ` [PATCH 6/8] perf data: Switch to multiple cpu stream files Jiri Olsa
2014-12-08 8:17 ` Namhyung Kim
2014-12-09 10:18 ` Jiri Olsa
2014-12-03 16:24 ` [PATCH 7/8] perf data: Enable stream flush within processing Jiri Olsa
2014-12-03 16:24 ` [PATCH 8/8] perf data: Add support for setting ordered_events queue size Jiri Olsa
2014-12-11 15:12 [PATCHv2 0/8] perf tools: Add perf data CTF conversion Jiri Olsa
2014-12-11 15:12 ` [PATCH 1/8] perf tools: Add feature check for libbabeltrace Jiri Olsa
2015-01-15 16:15 [PATCHv3 0/8] perf tools: Add perf data CTF conversion Jiri Olsa
2015-01-15 16:15 ` [PATCH 1/8] perf tools: Add feature check for libbabeltrace Jiri Olsa
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=20141209101416.GB2516@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=jgalar@efficios.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=tzanussi@gmail.com \
/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
all inboxes | Powered by JetHome®