This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: STAP depends on...
- From: Sebastien Decugis <sebastien dot decugis at ext dot bull dot net>
- To: Kevin Stafford <kevinrs at us dot ibm dot com>
- Cc: "Frank Ch. Eigler" <fche at redhat dot com>,William Cohen <wcohen at redhat dot com>, systemtap at sources dot redhat dot com
- Date: Thu, 27 Oct 2005 09:54:45 +0200
- Subject: Re: STAP depends on...
- Organization: Bull S.A.
- References: <435FB508.8080706@us.ibm.com>
Quick addition:
for some kernels (I think 2.6.9 to 2.6.11) you have to do the following
hack as well:
=================================
--- linux-2.6.11.prev/kernel/kallsyms.c 2005-09-28 18:18:22.000000000
+0200
+++ linux-2.6.11/kernel/kallsyms.c 2005-10-17 13:29:34.000000000 +0200
@@ -145,6 +145,7 @@
}
return module_kallsyms_lookup_name(name);
}
+EXPORT_SYMBOL(kallsyms_lookup_name);
/* Lookup an address. modname is set to NULL if it's in the kernel. */
const char *kallsyms_lookup(unsigned long addr,
==================================
Best regards,
Seb.
On Wed, 2005-10-26 at 09:55 -0700, Kevin Stafford wrote:
> During the last meeting there was discussion of posting some arch agnostic
> documentation regarding the various dependencies of SystemTap. The
> following
> is a sample list of configurations & utilities that SystemTap relies on.
>
> To build SystemTap from source, your system requires:
>
> Environment
> - Linux kernel v2.6.9+ with configs:
> CONFIG_KPROBES=y
> CONFIG_MODULES=y
> CONFIG_MODULE_UNLOAD=y
> CONFIG_MODULE_SIG=y
> CONFIG_DEBUG_INFO=y
>
> Development Tools
> - gawk
> - GNU make
> - gcc (-g debug enabled)
> - g++ (-g debug enabled)
>
> Standard Unix Binaries
> - (ln, egrep, mkdir, cd, rm, etc.)
>
> Extended Package Dependencies
> - elfutils-libelf-devel v0.115+
> - elfutils-libs v0.115+
> - elfutils-libelf v0.115+
> - elfutils-devel v0.115+
> - elfutils v0.115+
> * Some of the extended packages required for SystemTap
> rely on (often many) other packages. It is recommended
> you install such utilities using an automatic package
> resolution tool (yum, yast, apt, etc.)
>
> Before linking this off of the main website I would appreciate some
> feedback. Is
> there anything you can think of missing from the list?
>
> Tx.
>
--
Sebastien Decugis
Bull S.A.