aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-core/uclibc/uclibc-0.9.33.inc
diff options
context:
space:
mode:
authorTom Zanussi <tom.zanussi@intel.com>2012-08-31 00:06:57 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-09-02 05:47:43 -0700
commitc6da6b648328377ba3590fd38cb12dad26a46a13 (patch)
tree1e219e4e201a3a02f1f3ca24fbc5aacfbb8fe81e /meta/recipes-core/uclibc/uclibc-0.9.33.inc
parentbf9fa09109f172e85fab14dd3ad0cf22dbd7fd14 (diff)
downloadopenembedded-core-contrib-c6da6b648328377ba3590fd38cb12dad26a46a13.tar.gz
crosstap: new script
This script makes it easy to run a systemtap script on a remote target from a build host. The script itself contains documentation on basic setup and usage - see that for details. In a nutshell, if you have a systemtap script on the build host, this script allows that systemtap script to be compiled and run on the target host and for the output appear on the host terminal. The crosstap script requires to an sdk build of the target (or a build with 'tools-profile' added to EXTRA_IMAGE_FEATURES) because it needs to be able to run the native systemtap built by the systemtap recipe, which in turn needs access to the kernel built for the target in order to build the kernel modules that implement the systemtap probe specified by the systemtap script and which ultimately get shipped to the target and insmod'ed there. The crosstap script also needs to be able to ssh to the target host in order insert the modules on the target, so the target system needs to support incoming ssh connections. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
Diffstat (limited to 'meta/recipes-core/uclibc/uclibc-0.9.33.inc')
0 files changed, 0 insertions, 0 deletions