Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: ali.akyurek.ext@siemens.com (Akyurek, Ali (EXT))
Subject: [ltt-dev] the problem of using LTTNG on ARM
Date: Mon, 19 Jan 2009 10:17:59 +0100	[thread overview]
Message-ID: <1E65288790442545B413D69F2A8D27DE045EC4CC@ERLD164A.ww004.siemens.net> (raw)
Message-ID: <20090119091759.7MjiEUQlykwCD1ikW52vs3Ixib0rm7Wlnt2QoD8svLA@z> (raw)
In-Reply-To: <abc09c160901190046y640a2269p6ddaed37f562f81@mail.gmail.com>

Hi, exactly same problems i've met before.
 
1.It seems your shell doesn't have awk utility.I think you use
busybox.Just build busybox with  CONFIG_AWK = y 
 
Then you'll have awk.
 
2.Unable to find lttd. be sure that if you used a prefix while
configuring the ltt-ctl. Then ltt-ctl wants to find lttd in that folder.
For example i configured ltt-ctl as follows
 
./configure ... --prefix=/home/user/ltt
 
After make & make install lttd file is in my host folder
/home/user/ltt/bin/lttd
In the target, ltt-ctl searchs lttd in this path
(/home/user/ltt/bin/lttd).
 
Hope these help.


________________________________

Von: long xu [mailto:long.x.xu at gmail.com] 
Gesendet: Montag, 19. Januar 2009 09:47
An: ltt-dev at lists.casi.polymtl.ca
Betreff: [ltt-dev] the problem of using LTTNG on ARM




---------- Forwarded message ----------
From: long xu <long.x.xu@gmail.com>
Date: 2009/1/16
Subject: the problem of using LTTNG on ARM
To: mlm-lttv-dev-help at krystal.dyndns.org


HELLO,

I have built the ltt-control package for the ARM, 
and the command lttctl de lttd can work now.
But i can't crosse-build the markers-userspace, it
like that the markers-userspace can't support the ARM.

When i use the ltt-armall.sh, it trace like this:
-----------------------------------------------------------------------
ltt-armall.sh
Connecting all markers
/usr/bin/ltt-armall.sh: line 5: awk: not found
Connecting high-rate markers to tap
/usr/bin/ltt-armall.sh: line 41: awk: not found
-----------------------------------------------------------------------

and when i use the lttctl -C -w /tmp/trace1 trace1:
------------------------------------------------------------------------
--------
lttctl -C -w /tmp/trace1 trace1
Linux Trace Toolkit Trace Control 0.62-23122008

Controlling trace : trace1

lttctl: Creating trace
lttctl: Forking lttd
Error in executing the lttd daemon: No such file or directory
lttd process running failed
------------------------------------------------------------------------
--------

whether it need to install the markers-userspace before use 
the commands? or there is same other problems?

Thanks,

Best regard,

XU Long




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/ltt-dev/attachments/20090119/1ea97562/attachment.htm>


  parent reply	other threads:[~2009-01-19  9:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <abc09c160901160305w7875cee0r5017dbeda7702eef@mail.gmail.com>
2009-01-19  8:46 ` long xu
2009-01-19  8:46   ` long xu
2009-01-19  8:46   ` long xu
2009-01-19  9:17   ` Akyurek, Ali (EXT) [this message]
2009-01-19  9:17     ` Akyurek, Ali (EXT)
2009-01-19  9:17     ` Akyurek, Ali (EXT)

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=1E65288790442545B413D69F2A8D27DE045EC4CC@ERLD164A.ww004.siemens.net \
    --to=ali.akyurek.ext@siemens.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