This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Fwd: staprun-only system
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Jim Keniston <jkenisto at us dot ibm dot com>
- Cc: systemtap <systemtap at sources dot redhat dot com>, andmike at linux dot vnet dot ibm dot com
- Date: Tue, 21 Apr 2009 13:35:49 -0400
- Subject: Re: Fwd: staprun-only system
- References: <1240332739.3667.7.camel@dyn9047018094.beaverton.ibm.com>
Jim Keniston <jkenisto@us.ibm.com> forwarded:
> [...]
> I tried the ./configure on the target system and it did not generate a
> Makefile as the elfutils where not installed, I could install them, but
> since staprun does not need them I wanted to simplify my target system
> default install by not requiring extra rpms for debug.
We could add a configure option to disable building the translator,
and thus only build staprun/stapio.
> Since make install did not work. I copied the files by hand. I am still
> cleaning up a issue where staprun will not load the previously built
> scsi_test systemtap module.
> "# staprun ./scsi_test.ko
> ERROR: scsi_test: inconsistent scsi_mod build-id byte #0 (0x6e [actual]
> vs. 0x83 [debuginfo])"
This usually indicates a mismatch between the kernel build you've
targeted for the instrumentation and the kernel build you're trying to
run it on.
> Here is my current process.
>
> #On the Build system.
> [...]
> #On Target system.
> [...]
If you're already building the whole systemtap on your build machine,
was there some reason not to just copy the staprun/stapio executables
over to the target?
- FChE