From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>,
Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: --with-babeltrace generates many FAILs
Date: Wed, 20 Aug 2014 09:41:00 -0000 [thread overview]
Message-ID: <53F46D48.2060200@redhat.com> (raw)
In-Reply-To: <53F41DE5.1010406@codesourcery.com>
On 08/20/2014 05:02 AM, Yao Qi wrote:
> The patch is updated. OK to apply?
I'm wondering whether we really need all this complication for an old
version of a library that is quite new-ish, and not relied on for
anything really core? I'm wondering whether this check works on
Windows, for example.
As there's been fixed babeltrace versions for a while, I'd go with
simply dropping the workaround, and have integrators build newer
GDB with newer babeltrace. I suppose we have a testcase in our
testsuite that fails if we remove the workaround and GDB is built with
broken babeltrace? That should let the integrator know that it's
building again a broken lib.
IOW, why do we still need to support 1.1.0?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2014-08-20 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140816204614.GA7000@host2.jankratochvil.net>
2014-08-19 12:43 ` Yao Qi
2014-08-19 14:08 ` Jan Kratochvil
2014-08-20 4:06 ` Yao Qi
2014-08-20 9:41 ` Pedro Alves [this message]
2014-08-20 11:38 ` Yao Qi
2014-08-20 13:56 ` Pedro Alves
2014-08-21 4:57 ` Yao Qi
2014-08-21 12:48 ` Pedro Alves
2014-08-22 3:52 ` Yao Qi
2014-08-26 20:27 ` [for 7.8?] " Jan Kratochvil
2014-08-27 8:27 ` Yao Qi
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=53F46D48.2060200@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox