From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27467 invoked by alias); 22 Apr 2009 13:37:34 -0000 Received: (qmail 27460 invoked by uid 22791); 22 Apr 2009 13:37:34 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 22 Apr 2009 13:37:26 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n3MDb85G009645 for ; Wed, 22 Apr 2009 09:37:24 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n3MDb7i1008007 for ; Wed, 22 Apr 2009 09:37:07 -0400 Received: from localhost.localdomain (vpn-12-183.rdu.redhat.com [10.11.12.183]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n3MDb7rq021045; Wed, 22 Apr 2009 09:37:07 -0400 Message-ID: <49EF1D82.9070103@redhat.com> Date: Wed, 22 Apr 2009 13:37:00 -0000 From: David Smith User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: Mike Anderson CC: Jim Keniston , systemtap Subject: Re: Fwd: staprun-only system References: <1240332739.3667.7.camel@dyn9047018094.beaverton.ibm.com> <49EE0225.1010803@redhat.com> <20090422073952.GA30893@linux.vnet.ibm.com> In-Reply-To: <20090422073952.GA30893@linux.vnet.ibm.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2009-q2/txt/msg00376.txt.bz2 Mike Anderson wrote: > David Smith wrote: >> 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. >> > > Thanks for the response. While this is an option I was trying to avoid > setting up build environments matching all the test machines that I have. > The test systems may be of more than one distro type and library versions. You might be making more work for yourself in trying to avoid setting up build environments. Besides setting up actual machines to match all your environments, there are other options of mock or virtual machines. >> 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. > > In my previous example my configure and make steps where pretty close to > the what the spec file is doing. Copying the runtime files over to the > target system assumes that they are like enough that the commands will > run. I'm confused. Are you only building once and then deploying on multiple target platforms? -- David Smith dsmith@redhat.com Red Hat http://www.redhat.com 256.217.0141 (direct) 256.837.0057 (fax)