This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: --with-babeltrace generates many FAILs
- From: Pedro Alves <palves at redhat dot com>
- To: Yao Qi <yao at codesourcery dot com>, Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Wed, 20 Aug 2014 10:41:28 +0100
- Subject: Re: --with-babeltrace generates many FAILs
- Authentication-results: sourceware.org; auth=none
- References: <20140816204614 dot GA7000 at host2 dot jankratochvil dot net> <53F3457E dot 5030205 at codesourcery dot com> <20140819140755 dot GA30208 at host2 dot jankratochvil dot net> <53F41DE5 dot 1010406 at codesourcery dot 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