From: Peter Zijlstra <peterz@infradead.org>
To: Ian Rogers <irogers@google.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Steven Rostedt <rostedt@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH v1 1/2] perf build: Require libtraceevent from the system
Date: Fri, 18 Nov 2022 10:30:45 +0100 [thread overview]
Message-ID: <Y3dQxVNwGmQMWPP0@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20221117224952.358639-2-irogers@google.com>
On Thu, Nov 17, 2022 at 02:49:51PM -0800, Ian Rogers wrote:
> Unconditionally require libtraceevent to come from the system. Force
> the determination of the libtracefs version if it is present.
-ENOMOTIVATION
also:
Makefile.config:1196: *** Error: libtraceevent is missing, please install libtraceevent-dev. Stop.
Why do I need this?
next prev parent reply other threads:[~2022-11-18 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 22:49 [PATCH v1 0/2] perf always use system libtraceevent Ian Rogers
2022-11-17 22:49 ` [PATCH v1 1/2] perf build: Require libtraceevent from the system Ian Rogers
2022-11-18 9:30 ` Peter Zijlstra [this message]
2022-11-18 15:02 ` Arnaldo Carvalho de Melo
2022-11-18 15:33 ` Steven Rostedt
2022-11-18 16:34 ` Arnaldo Carvalho de Melo
2022-11-19 0:37 ` Namhyung Kim
2022-11-17 22:49 ` [PATCH v1 2/2] tools lib traceevent: Remove libtraceevent Ian Rogers
2022-11-17 23:16 ` Steven Rostedt
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=Y3dQxVNwGmQMWPP0@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rostedt@google.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).