From: Steven Rostedt <rostedt@goodmis.org>
To: Johannes Berg <johannes@sipsolutions.net>,
"linux-trace-devel@vger.kernel.org"
<linux-trace-devel@vger.kernel.org>
Cc: Tzvetomir Stoyanov <tstoyanov@vmware.com>
Subject: Re: trace-cmd python
Date: Thu, 3 Jan 2019 22:43:00 -0500 [thread overview]
Message-ID: <20190103224300.418e002b@vmware.local.home> (raw)
In-Reply-To: <1524143246.3024.21.camel@sipsolutions.net>
On Thu, 19 Apr 2018 15:07:26 +0200
Johannes Berg <johannes@sipsolutions.net> wrote:
Hi Johannes,
This was buried in my TODO list, and lost. I just noticed it.
> So, starting again from git clean -fdxq, I observe the following:
>
> 1) make -j8 install
> -> errors out with
> "make[1]: *** No rule to make target '/home/jberg1/sys/trace-cmd/lib/trace-cmd/libtracecmd.a', needed by 'ctracecmd.so'. Stop."
>
> 2) make install
> -> python plugin not installed
> -> copy it manually
>
> 3) running trace-cmd report with plugin_mac80211.py in
> ~/.trace-cmd/plugins/ I see
>
> failed loading /home/jberg1/.trace-cmd/plugins/mac80211.py
> Traceback (most recent call last):
> File "<string>", line 1, in <module>
> File "/tmp/tcmd//lib/trace-cmd/python/tracecmd.py", line 22, in <module>
> from ctracecmd import *
> ImportError: /tmp/tcmd//lib/trace-cmd/python/ctracecmd.so: undefined symbol: traceevent_plugin_free_options_list
>
> If I remove that from the header file I eventually get down to not
> having __vpr_stat() or something, which seems to indicate that
> ctracecmd.so isn't linked with libtraceevent, only with libtracecmd? But
> adding that to the Makefile didn't change anything, and then I gave up
> and checked out v2.7 instead.
>
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 :-( )
-- Steve
next parent reply other threads:[~2019-01-04 3:43 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 ` Steven Rostedt [this message]
2019-01-09 20:36 ` trace-cmd python Steven Rostedt
2019-01-15 13:09 ` Johannes Berg
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=20190103224300.418e002b@vmware.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).