All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Hui Zhu <teawater@gmail.com>
Cc: Yao Qi <yao@codesourcery.com>,
	gdb-patches@sourceware.org, Pedro Alves <palves@redhat.com>,
	lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: [PATCH 3/5] Read CTF by the ctf target
Date: Tue, 7 May 2013 09:07:41 -0400	[thread overview]
Message-ID: <20130507130741.GE4186@Krystal> (raw)
In-Reply-To: <CANFwon2TPo1X2cUXXdzDEnX3UPvG2w0ZNMpNGN=KoDdBvyXLFQ@mail.gmail.com>

* Hui Zhu (teawater@gmail.com) wrote:
> On Fri, Mar 1, 2013 at 1:18 AM, Pedro Alves <palves@redhat.com> wrote:
> > (not a complete review)
> >
> > On 02/27/2013 02:17 AM, Yao Qi wrote:
> >
> >> +if test "x$with_babeltrace" != "xno"; then
> >> +  saved_CFLAGS="$CFLAGS"
> >> +  CFLAGS="$CFLAGS $btinc"
> >> +  AC_MSG_CHECKING([for babeltrace])
> >> +  AC_TRY_COMPILE([
> >> +#include <babeltrace/babeltrace.h>
> >> +#include <babeltrace/ctf/events.h>
> >> +#include <babeltrace/ctf/iterator.h>
> >
> > We know from previous patches that the latest released
> > babeltrace breaks gdb, due to the lookup_enum function.  Does
> > this catch that?  I see namespacing fixes going into
> > babeltrace as recently as last 15th.  Do we know if
> > babeltrace's API is more or less done and close to a release?
> 
> Hi Mathieu,
> 
> Could you help us with this question?

We did the 1.1.0 release specifically for namespace fixes on March 23rd.

commit c99b1910bea848e8f0ae5641bb63b8f4f84f3ec0
Author: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Date:   Sat Mar 23 13:34:22 2013 -0400

    Version 1.1.0
    
    Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>

Thanks,

Mathieu


> 
> Thanks,
> Hui
> 
> >
> >> +  ],[],
> >> +  [AC_MSG_RESULT([yes]); AC_DEFINE(HAVE_LIBBABELTRACE, 1, [Define if libbabeltrace is available])],
> >> +  [AC_MSG_RESULT([no]); btlibs= ; btinc= ])
> >> +  CFLAGS="$saved_CFLAGS"
> >> +fi
> >> +
> >> +# Flags needed for UST
> >
> > babeltrace
> >
> >> +AC_SUBST(btlibs)
> >> +AC_SUBST(btinc)
> >> +
> >
> > --
> > Pedro Alves
> >

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

  reply	other threads:[~2013-05-07 13:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1361931459-3953-1-git-send-email-yao@codesourcery.com>
     [not found] ` <1361931459-3953-4-git-send-email-yao@codesourcery.com>
     [not found]   ` <512F9182.3080104@redhat.com>
2013-03-01  2:37     ` [PATCH 3/5] Read CTF by the ctf target Hui Zhu
2013-05-07 13:07       ` Mathieu Desnoyers [this message]
2013-05-07 13:24         ` Yao Qi
2013-05-07 13:28           ` Mathieu Desnoyers

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=20130507130741.GE4186@Krystal \
    --to=mathieu.desnoyers@efficios.com \
    --cc=gdb-patches@sourceware.org \
    --cc=lttng-dev@lists.lttng.org \
    --cc=palves@redhat.com \
    --cc=teawater@gmail.com \
    --cc=yao@codesourcery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.