public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/6925] New: make roland happy
Date: Mon, 29 Sep 2008 23:53:00 -0000	[thread overview]
Message-ID: <20080929235151.6925.fche@redhat.com> (raw)

See http://sourceware.org/ml/systemtap/2008-q3/msg00809.html

I see a few separate issues:

* running stap without a make install
  We could help by having the Makefile print out instructions
  about how to use stap from the build tree (for a make all)
  or the install tree (for a make install):

  % make
    [...]
    We recommend you "make install", but if you wish, you may
    run systemtap out of this build tree using these environment
    variables:
    env SYSTEMTAP_RUNTIME=......  

  % make install
    [...]
    We commend you upon your wise decision to install systemtap.
    You just need $prefix/bin in your $PATH and you're ready to enjoy.

  Yeah, the man page could help too.

* stap -r /BUILD/TREE should work better
  This is bug #5892, with some extras.  q.v.

* make verbosity a pass-dependent thing
  I don't know off-hand what to do ... maybe extend the "-p NUM"
  syntax to add an associated verbosity level for the duration.

* let stap find staprun and stapio in $PATH too
  The solution would be to extend $PATH with $prefix/libexec,
  or stat and execvp if $execdir/.../stap{run,io} don't exist.

* make staprun clean up before & after itself better w.r.t.
  loaded modules if something with stapio goes wrong

-- 
           Summary: make roland happy
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: fche at redhat dot com
 BugsThisDependsOn: 5892


http://sourceware.org/bugzilla/show_bug.cgi?id=6925

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

             reply	other threads:[~2008-09-29 23:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-29 23:53 fche at redhat dot com [this message]
2008-09-30 13:08 ` Eugeniy Meshcheryakov
2008-09-30 18:04 ` [Bug translator/6925] " pmuller at redhat dot com
2008-11-18 21:50 ` fche at redhat dot com
2008-12-03 18:41 ` fche at redhat dot com
2008-12-03 22:31 ` fche at redhat dot com
2008-12-03 22:54 ` roland at gnu dot org
2008-12-03 22:59 ` roland at gnu dot org
2008-12-07 15:21 ` fche at redhat dot com
2008-12-07 15:21 ` fche at redhat dot com
2008-12-07 21:53 ` fche at redhat dot com
2008-12-07 22:32 ` roland at gnu dot org
2008-12-29 21:11 ` fche at redhat dot com
2009-01-05  5:28 ` wenji dot huang at oracle dot com
2009-02-04 22:43 ` fche at redhat dot com

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=20080929235151.6925.fche@redhat.com \
    --to=sourceware-bugzilla@sourceware.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).