From: "Frank Ch. Eigler" <fche@redhat.com>
To: Da Zheng <zhengda1936@gmail.com>
Cc: Mark Wielaard <mjw@redhat.com>, systemtap@sourceware.org
Subject: Re: error to run systemtap in an ARM platform
Date: Fri, 15 Jul 2011 20:50:00 -0000 [thread overview]
Message-ID: <20110715205023.GA30682@redhat.com> (raw)
In-Reply-To: <4E20A714.9020404@gmail.com>
Hi -
On Fri, Jul 15, 2011 at 01:46:12PM -0700, Da Zheng wrote:
> [...]
> Yes, right now what I can do is to ask stap to keep the source code of
> the translated module, and then enter the directory of source code and run
> make -C
> /build/tegra2_seaboard/tmp/portage/sys-kernel/chromeos-kernel-9999/work/chromeos-kernel-9999/build/tegra2_seaboard
> M=`pwd` ARCH=arm CROSS_COMPILE=armv7a-cros-linux-gnueabi- modules
> It works, but it's not very convenient.
Use the stap -B flag, ie.
% stap -a arm -B CROSS_COMPILE=armv7a-cros-linux-gnueabi- <etc>
- FChE
next prev parent reply other threads:[~2011-07-15 20:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 0:58 Da Zheng
2011-07-15 9:43 ` Mark Wielaard
2011-07-15 20:00 ` Da Zheng
2011-07-15 20:15 ` Frank Ch. Eigler
[not found] ` <4E20A714.9020404@gmail.com>
2011-07-15 20:50 ` Frank Ch. Eigler [this message]
2011-07-15 20:46 ` William Cohen
2011-07-15 21:29 ` Da Zheng
2011-07-16 0:23 ` Turgis, Frederic
2011-07-18 14:13 ` William Cohen
2011-07-18 19:02 ` Da Zheng
2011-07-18 20:10 ` William Cohen
2011-07-18 20:18 ` William Cohen
2011-07-18 20:41 ` Da Zheng
2011-07-23 22:56 ` Zheng Da
2011-07-24 1:57 ` Frank Ch. Eigler
2011-07-24 16:10 ` Frank Ch. Eigler
2011-07-25 10:04 ` Mark Wielaard
2011-07-25 19:34 ` Da Zheng
2011-07-25 15:46 ` William Cohen
2011-07-25 19:36 ` Da Zheng
2011-07-25 20:46 ` Mark Wielaard
2011-07-25 17:17 ` William Cohen
2011-07-25 19:56 ` Da Zheng
2011-07-26 14:03 ` William Cohen
2011-07-26 17:47 ` Da Zheng
2011-07-19 11:38 ` Turgis, Frederic
2011-07-18 14:00 ` William Cohen
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=20110715205023.GA30682@redhat.com \
--to=fche@redhat.com \
--cc=mjw@redhat.com \
--cc=systemtap@sourceware.org \
--cc=zhengda1936@gmail.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).