From: Steven Rostedt <rostedt@goodmis.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-trace-devel@vger.kernel.org"
<linux-trace-devel@vger.kernel.org>,
Tzvetomir Stoyanov <tstoyanov@vmware.com>
Subject: Re: trace-cmd python
Date: Tue, 15 Jan 2019 09:44:51 -0500 [thread overview]
Message-ID: <20190115094451.119784d5@gandalf.local.home> (raw)
In-Reply-To: <b8e933bd8fc5f6a1aac94beced2ee75b8729975b.camel@sipsolutions.net>
On Tue, 15 Jan 2019 14:09:30 +0100
Johannes Berg <johannes@sipsolutions.net> wrote:
> Seems to work more or less.
>
> Not sure how I managed to install it into a custom subdirectory of my
> $HOME before, and make it load plugins - I can't seem to figure out the
> right combination of prefix= and DESTDIR= anymore.
DESTDIR is where you want to install it for moving it to another
machine. If you plan on running trace-cmd on the same machine, but
having it look elsewhere, then just using prefix should be enough.
>
> If I symlink it to a place where trace-cmd actually looks for it then I
> get errors in python saying pevent_record_data_get() is not defined, but
Looks to be an old object that it's linking with, as we replaced all
"pevent_" with "tep_".
> could be that I'm not importing something right ...
>
> What's a good way to install it into a custom directory without
> affecting the whole machine?
The prefix tells the build to have the executables search that path.
The DESTDIR is for installing in a particular location that you will
move that code to another machine.
e.g.
make prefix=/usr/local DESTDIR=/tmp/tracecmd install
Will install the executables in /tmp/tracecmd, but when you run those
executables, they will want to look in the /usr/local path.
It should also always search your home directory in ".trace-cmd/plugins"
-- Steve
next prev parent reply other threads:[~2019-01-15 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1524143246.3024.21.camel@sipsolutions.net>
2019-01-04 3:43 ` trace-cmd python Steven Rostedt
2019-01-09 20:36 ` Steven Rostedt
2019-01-15 13:09 ` Johannes Berg
2019-01-15 14:44 ` Steven Rostedt [this message]
2019-01-19 9:12 ` Johannes Berg
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=20190115094451.119784d5@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=johannes@sipsolutions.net \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tstoyanov@vmware.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 NNTP newsgroup(s).