From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Jiri Olsa <jolsa@redhat.com>
Cc: linux-kernel@vger.kernel.org, lttng-dev@lists.lttng.org,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
acme@kernel.org, namhyung.kim@lge.com, tzanussi@gmail.com
Subject: Re: [RFC] perf to ctf converter
Date: Tue, 22 Jul 2014 08:58:17 +0200 [thread overview]
Message-ID: <53CE0B89.7030400@linutronix.de> (raw)
In-Reply-To: <20140721183530.GA28673@krava.redhat.com>
On 07/21/2014 08:35 PM, Jiri Olsa wrote:
> On Mon, Jul 21, 2014 at 07:11:51PM +0200, Sebastian Andrzej Siewior wrote:
>
> heya,
> I've got following build error:
>
> CC util/data-bt.o
> util/data-bt.c: In function ‘add_event_tracepoint_value’:
> util/data-bt.c:293:3: error: implicit declaration of function ‘bt_ctf_event_class_get_field_by_name’ [-Werror=implicit-function-declaration]
> type = bt_ctf_event_class_get_field_by_name(
> ^
> util/data-bt.c:293:3: error: nested extern declaration of ‘bt_ctf_event_class_get_field_by_name’ [-Werror=nested-externs]
> util/data-bt.c:293:8: error: assignment makes pointer from integer without a cast [-Werror]
> type = bt_ctf_event_class_get_field_by_name(
> ^
> cc1: all warnings being treated as errors
> make[1]: *** [util/data-bt.o] Error 1
> make: *** [all] Error 2
>
>
> but I might be missing some of the babeltrace changes, my branch:
> 5805251d8079 Fix: mmap trace read the stream_id from the first packet
Hmm. This function should be there as of commit 2f100782231 in the
master branch. However since my first post and now the babeltrace
source got moved around a little and as a result you have some more
header files.
The function in question is defined in "babeltrace/ctf-ir/event.h" and
included by "babeltrace/ctf-writer/event.h".
> feel free to use/change my commits as you wish ;-)
Thank you.
>
> I think the best would be to merge your changes with mine
> into some meaningful patchset, before it goes to review
Yeah. I merged some of the fixups back and for the data-bt.c changes,
dunno. Either all my changes as a single patch or merge it back into
yours as it doesn't make sense to post each incremental change.
> I'll check your changes
>
> thanks,
> jirka
>
Sebastian
next prev parent reply other threads:[~2014-07-22 6:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 16:36 [RFC] perf to ctf converter Sebastian Andrzej Siewior
2014-07-14 14:15 ` Jiri Olsa
2014-07-18 12:34 ` Sebastian Andrzej Siewior
2014-07-18 16:12 ` Sebastian Andrzej Siewior
2014-07-21 15:36 ` Mathieu Desnoyers
2014-08-05 14:51 ` [lttng-dev] " Jérémie Galarneau
2014-08-05 14:57 ` Sebastian Andrzej Siewior
2014-07-21 17:11 ` Sebastian Andrzej Siewior
2014-07-21 18:35 ` Jiri Olsa
2014-07-22 6:58 ` Sebastian Andrzej Siewior [this message]
2014-07-22 11:25 ` Jiri Olsa
2014-07-22 11:31 ` Sebastian Andrzej Siewior
2014-07-22 13:31 ` Sebastian Andrzej Siewior
2014-07-24 14:46 ` Jiri Olsa
2014-07-25 8:37 ` Sebastian Andrzej Siewior
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=53CE0B89.7030400@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lttng-dev@lists.lttng.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=namhyung.kim@lge.com \
--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;
as well as URLs for NNTP newsgroup(s).