public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mjw@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: systemtap@sources.redhat.com
Subject: Re: /usr/bin/staprun hardcoded in latest git
Date: Sun, 04 Jan 2009 18:30:00 -0000	[thread overview]
Message-ID: <1231093835.3380.21.camel@hermans.wildebeest.org> (raw)
In-Reply-To: <20090104141653.GA6183@basil.nowhere.org>

Hi Andi,

On Sun, 2009-01-04 at 15:16 +0100, Andi Kleen wrote:
> I updated to a recent git version of systemtap. One issue I noticed
> is that /usr/sbin/staprun is hardcoded somewhere in stap (I didn't find
> it with a quick grep in the source, but according to strings it is in
> stapio). I had it installed in /usr/local/bin
> and "stap" failed because it couldn't find /usr/bin/staprun.
> I worked around it with a symlink, but it should be probably fixed.

Thanks for the report. stapio gets staprun through:
const char *staprun = getenv ("SYSTEMTAP_STAPRUN") ?: BINDIR "/staprun";
So, you can also work around it by setting SYSTEMTAP_STAPRUN to your
local staprun. But BINDIR should default to '${exec_prefix}/bin' unless
you configure --bindir=/something/else. I am not sure how it could have
been set to /usr/sbin in your case. Maybe config.log gives a hint how
bindir was set?

> The other issue was that the new NSS dependency is somewhat 
> annoying. I hope systemtap doesn't plan to descend further
> into DLL hell territory.

The NSS dependency is only needed for the client/server mode. It would
be good to have a configure --disable-stap-sever for those that don't
need it (or disable building it automagically when NSS isn't found).

Cheers,

Mark

  reply	other threads:[~2009-01-04 18:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-04 14:15 Andi Kleen
2009-01-04 18:30 ` Mark Wielaard [this message]
2009-01-04 18:42   ` Andi Kleen
2009-01-04 19:11     ` Mark Wielaard
2009-01-04 19:31       ` Andi Kleen
2009-01-05  9:59         ` Mark Wielaard
2009-01-05 12:42           ` Andi Kleen
2009-01-11 13:47             ` Mark Wielaard
2009-01-05 16:09       ` Dave Brolley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1231093835.3380.21.camel@hermans.wildebeest.org \
    --to=mjw@redhat.com \
    --cc=andi@firstfloor.org \
    --cc=systemtap@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).