From: victorcora98@gmail.com
To: linux-trace-devel@vger.kernel.org
Cc: Victor Cora Colombo <victorcora98@gmail.com>
Subject: [PATCH v2] trace-cmd: Add dependencies to BUILDING section in README
Date: Fri, 13 Aug 2021 16:25:16 -0300 [thread overview]
Message-ID: <20210813192516.24872-1-victorcora98@gmail.com> (raw)
From: Victor Cora Colombo <victorcora98@gmail.com>
KernelShark has instructions in its README on how to get necessary
dependencies to build it. trace-cmd could follow this example and
also add more information on how to build it.
This patch adds instructions to README on how to get necessary libraries
and dependencies to build trace-cmd.
Signed-off-by: Victor Cora Colombo <victorcora98@gmail.com>
---
README | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/README b/README
index 1153152..094fce1 100644
--- a/README
+++ b/README
@@ -24,6 +24,23 @@ Lesser General Public License 2.1 (See COPYING.LIB).
BUILDING:
+In order to install build dependencies on Ubuntu do the following:
+ sudo apt-get install build-essential git pkg-config -y
+
+In order to install build dependencies on Fedora, as root do the following:
+ dnf install gcc make git pkg-config -y
+
+To install required dependencies:
+ git clone https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git/
+ cd libtraceevent
+ make
+ sudo make install
+
+ git clone https://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git/
+ cd libtracefs
+ make
+ sudo make install
+
To make trace-cmd
make
--
2.32.0
next reply other threads:[~2021-08-13 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 19:25 victorcora98 [this message]
2021-08-19 19:42 ` [PATCH v2] trace-cmd: Add dependencies to BUILDING section in README Steven Rostedt
2021-08-20 0:25 ` Victor Cora Colombo
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=20210813192516.24872-1-victorcora98@gmail.com \
--to=victorcora98@gmail.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).