Re: Fwd: staprun-only system

[David Smith <dsmith at redhat dot com>]

Jim Keniston wrote:
> Here's email from Mike Anderson, an IBMer who has been using SystemTap
> for some time.  As indicated, the staprun-only build is not working for
> him as desired, and he has taken considerable pains to work around the
> failures he sees.
> 
> I'm forwarding this with his permission in hopes that someone can give
> him some guidance.
> 
> Thanks.
> Jim
> -------- Forwarded Message --------
> From: Mike Anderson <andmike@linux.vnet.ibm.com>
> To: jkenisto@linux.vnet.ibm.com
> Subject: Re: staprun-only system
> Date: Fri, 17 Apr 2009 13:50:20 -0700
> 
> jkenisto@linux.vnet.ibm.com wrote:
>>    Hi, Mike.  We talked about your desire for a stripped-down staprun-only
>>    build.  This is supposed to be supported.  The simplest approach,
>>    according to Frank Eigler, is to do:
>>    $ ./configure     # Ignore messages about missing components.
>>    $ make staprun
>>
>>    I haven't tried this.
>>
>>    There's also documentation about this in Section 2.2 in the SystemTap
>>    Beginner's Guide (see
>>    [1]http://sourceware.org/systemtap/documentation.html).
>>
> 
> Thanks for the email.
> 
> The -g (guru) mode solved my blacklist issue.
> "... guru mode enabled - ignoring blacklist ..."
> 
> On the stripped down staprun for the target system here is what I
> observed using the current systemtap git tree (systemtap-0.9.5-25620).

... steps deleted ...

Assuming you are using an rpm-based system, here's what you should do.
Install your distro-supplied 'systemtap-runtime' rpm on the target system.

If you want the latest .git version, you would do something like the
following on your build system:

1.) Pull latest systemtap git tree.
2.) Generate tar file from git tree
3.) Run rpmbuild on the tar file and spec file.  Something like:
    # rpmbuild --define "_topdir `pwd`" --define "_sourcedir `pwd`" -bb
systemtap.spec
4.) Copy RPMS/{ARCH}/systemtap-runtime-*.rpm to the target system
5.) Install the systemtap-runtime rpm on the target system.
6.) Install RPMS/{ARCH}/systemtap-* rpms on the build system (minus the
debuginfo rpm and probably the testsuite rpm)

Now you have matching systemtap versions on both your build and target
systems.

If you aren't using an rpm-based system, I'd basically mimic what the
spec file does.  Configure and build, then copy the files mentioned in
the '%files runtime' section over to the target system.

-- 
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)