From: Johannes Berg <johannes@sipsolutions.net>
To: Steven Rostedt <rostedt@goodmis.org>,
"linux-trace-devel@vger.kernel.org"
<linux-trace-devel@vger.kernel.org>
Cc: Tzvetomir Stoyanov <tstoyanov@vmware.com>
Subject: Re: trace-cmd python
Date: Tue, 15 Jan 2019 14:09:30 +0100 [thread overview]
Message-ID: <b8e933bd8fc5f6a1aac94beced2ee75b8729975b.camel@sipsolutions.net> (raw)
In-Reply-To: <20190109153650.0261951b@gandalf.local.home>
On Wed, 2019-01-09 at 15:36 -0500, Steven Rostedt wrote:
> On Thu, 3 Jan 2019 22:43:00 -0500
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
>
> > I just checked, and this is still an issue today. I'll make sure that
> > this gets fixed soon.
> >
> > Thanks for reporting! (even though it got lost in my INBOX :-( )
> >
>
> OK, I finally got around to looking at this. It was a bit of a pain to
> figure out. It was caused by the shuffling of the files around, as that
> was needed to do because trace-cmd was getting bigger. This caused the
> python ctracecmd.so to lose linking with the proper libraries and
> caused the undefined symbols.
>
> I just fixed it and pushed it to the repo. Want to give it a try and
> see if it works for you?
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.
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
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?
johannes
next prev parent reply other threads:[~2019-01-15 13:09 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 [this message]
2019-01-15 14:44 ` Steven Rostedt
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=b8e933bd8fc5f6a1aac94beced2ee75b8729975b.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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).