From: Yao Qi <yao@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [RFC v2 2/9] move some rsp bits into rsp-low.h
Date: Fri, 14 Feb 2014 01:36:00 -0000 [thread overview]
Message-ID: <52FD728B.3070405@codesourcery.com> (raw)
In-Reply-To: <87r477qcds.fsf@fleche.redhat.com>
On 02/13/2014 11:07 PM, Tom Tromey wrote:
> Yao> We also need to compile rsp-low.c for IPA, and link rsp-low-ipa.o
> Yao> in IPA. I get the ipa build error below,
>
> Sorry Yao.
> Could you mention again what version of UST is supported?
> I tried just now with:
>
> barimba. rpm -q lttng-ust-devel
> lttng-ust-devel-2.0.8-1.fc18.x86_64
>
> but it doesn't work:
>
> checking for ust... no
Mine is UST 0.11 and URCU 0.5.3. GDB support in UST was removed in
release 0.12
(http://git.lttng.org/?p=ust.git;a=commit;h=fe566790e6be3f27f0befd85b715a3e84977bf6c).
Only UST 0.11 works for
GDB, IIRC.
--
Yao (é½å°§)
next prev parent reply other threads:[~2014-02-14 1:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 19:29 [RFC v2 0/9] move more code into common/ Tom Tromey
2014-02-06 19:29 ` [RFC v2 3/9] don't let bin2hex call strlen Tom Tromey
2014-02-06 19:29 ` [RFC v2 1/9] share "cell" code Tom Tromey
2014-02-06 19:29 ` [RFC v2 4/9] don't let hexify call strlen Tom Tromey
2014-02-06 19:29 ` [RFC v2 2/9] move some rsp bits into rsp-low.h Tom Tromey
2014-02-13 9:02 ` Yao Qi
2014-02-13 10:38 ` Pedro Alves
2014-02-14 2:00 ` Yao Qi
2014-02-13 15:08 ` Tom Tromey
2014-02-14 1:36 ` Yao Qi [this message]
2014-02-06 19:38 ` [RFC v2 5/9] replace hexify with bin2hex Tom Tromey
2014-02-06 19:41 ` [RFC v2 6/9] replace convert_int_to_ascii " Tom Tromey
2014-02-06 20:23 ` [RFC v2 7/9] replace unhexify with hex2bin Tom Tromey
2014-02-06 20:23 ` [RFC v2 8/9] replace convert_ascii_to_int " Tom Tromey
2014-02-06 20:24 ` [RFC v2 9/9] update rsp-low comments Tom Tromey
2014-02-07 12:53 ` [RFC v2 0/9] move more code into common/ Pedro Alves
2014-02-12 16:57 ` Tom Tromey
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=52FD728B.3070405@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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