From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: alialnu@nvidia.com, Matan Azrad <matan@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>
Subject: [PATCH] doc: update recipe for static rdma-core in mlx guides
Date: Thu, 8 Dec 2022 12:16:46 +0100 [thread overview]
Message-ID: <20221208111646.1487459-1-thomas@monjalon.net> (raw)
With recent versions of rdma-core, it becomes important to install,
so some non-standard compiler tricks are avoided.
While at it, disabling unneeded pyVerbs and man pages.
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
doc/guides/nics/mlx4.rst | 3 ++-
doc/guides/platform/mlx5.rst | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/doc/guides/nics/mlx4.rst b/doc/guides/nics/mlx4.rst
index 924ce6f64b..c6279f51d0 100644
--- a/doc/guides/nics/mlx4.rst
+++ b/doc/guides/nics/mlx4.rst
@@ -209,8 +209,9 @@ Current RDMA core package and Linux kernel (recommended)
- Starting with rdma-core v21, static libraries can be built::
cd build
- CFLAGS=-fPIC cmake -DIN_PLACE=1 -DENABLE_STATIC=1 -GNinja ..
+ CFLAGS=-fPIC cmake -DENABLE_STATIC=1 -DNO_PYVERBS=1 -DNO_MAN_PAGES=1 -GNinja ..
ninja
+ ninja install
.. _`RDMA core installation documentation`: https://raw.githubusercontent.com/linux-rdma/rdma-core/master/README.md
diff --git a/doc/guides/platform/mlx5.rst b/doc/guides/platform/mlx5.rst
index 3cc1dd29e2..5784b9a87b 100644
--- a/doc/guides/platform/mlx5.rst
+++ b/doc/guides/platform/mlx5.rst
@@ -162,8 +162,9 @@ https://github.com/linux-rdma/rdma-core
It is possible to build rdma-core as static libraries starting with version 21::
cd build
- CFLAGS=-fPIC cmake -DIN_PLACE=1 -DENABLE_STATIC=1 -GNinja ..
+ CFLAGS=-fPIC cmake -DENABLE_STATIC=1 -DNO_PYVERBS=1 -DNO_MAN_PAGES=1 -GNinja ..
ninja
+ ninja install
NVIDIA MLNX_OFED/EN
--
2.38.1
next reply other threads:[~2022-12-08 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 11:16 Thomas Monjalon [this message]
2022-12-08 11:33 ` Bruce Richardson
2023-01-11 8:45 ` [PATCH v2] " Thomas Monjalon
2023-03-07 11:16 ` Raslan Darawsheh
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=20221208111646.1487459-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=alialnu@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=viacheslavo@nvidia.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).