From: Steven Rostedt <rostedt@goodmis.org>
To: Ian Rogers <irogers@google.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: libtraceevent and copy in linux/tools
Date: Tue, 20 Apr 2021 23:27:14 -0400 [thread overview]
Message-ID: <20210420232714.43925af0@oasis.local.home> (raw)
In-Reply-To: <CAP-5=fWSDxOxBsoK8koaNbJwTVgjJwzoVe1jYuoX-Vhvteqcqg@mail.gmail.com>
On Tue, 20 Apr 2021 20:09:25 -0700
Ian Rogers <irogers@google.com> wrote:
> Hi,
>
> libtracefs [1] has a dependency on tep_vwarning which is declared in
> libtraceevent [2]. The libtraceevent in linux/tools lacks this [3] and
> so trace-cmd, that requires libtracefs, can only be built with the
> separate libtraceevent. I'm trying to avoid having two libtraceevent.
> Should the copy in linux/tools be updated or should I not be using
> that any more?
Yes, the libtraceevent in the linux kernel is deprecated, and once
libtraceveent is available in all major distros (from the separate
library), we will be removing it from the kernel and having perf use
the library version.
-- Steve
prev parent reply other threads:[~2021-04-21 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 3:09 libtraceevent and copy in linux/tools Ian Rogers
2021-04-21 3:27 ` Steven Rostedt [this message]
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=20210420232714.43925af0@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=irogers@google.com \
--cc=linux-trace-devel@vger.kernel.org \
/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).