From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
Subject: [commit] babeltrace compilation regression [Re: [PATCH] Avoid non-C++-enabled babeltrace versions]
Date: Tue, 05 Jul 2016 08:50:00 -0000 [thread overview]
Message-ID: <20160705084948.GA32506@host1.jankratochvil.net> (raw)
In-Reply-To: <m3bn2dvltd.fsf@oc1027705133.ibm.com>
On Mon, 04 Jul 2016 10:39:42 +0200, Andreas Arnez wrote:
> On Sun, Jul 03 2016, Jan Kratochvil wrote:
> > Have you tested that your line
> > pos.type = BT_SEEK_BEGIN;
> > with some libbabeltrace version or was that just a typo?
>
> Phew, curious... this sure looks like a typo. IIRC, I've tested that
> GDB *builds*, but probably forgot to verify that the babeltrace
> configure check actually succeeds. Sorry about that.
Checked in as obvious:
13cdc2afb7873547ec2910ba647fb4a68602252f
Jan
prev parent reply other threads:[~2016-07-05 8:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 11:16 [PATCH] Avoid non-C++-enabled babeltrace versions Andreas Arnez
2016-04-27 12:02 ` Pedro Alves
2016-04-27 14:24 ` Andreas Arnez
2016-07-03 15:43 ` [patch] babeltrace compilation regression [Re: [PATCH] Avoid non-C++-enabled babeltrace versions] Jan Kratochvil
2016-07-04 8:39 ` Andreas Arnez
2016-07-05 8:50 ` Jan Kratochvil [this message]
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=20160705084948.GA32506@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).