From: Ali Alnubani <alialnu@mellanox.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "gavin.hu@arm.com" <gavin.hu@arm.com>,
"joyce.kong@arm.com" <joyce.kong@arm.com>,
"ruifeng.wang@arm.com" <ruifeng.wang@arm.com>
Subject: [dpdk-dev] [PATCH] doc: use the latest numactl release
Date: Wed, 27 Nov 2019 15:23:18 +0000 [thread overview]
Message-ID: <20191127152259.29424-1-alialnu@mellanox.com> (raw)
Previous versions of numactl may produce the following error
on some systems (at least on Fedora 30 and RHEL7.4):
./.libs/libnuma.so: undefined reference to `minor'
./.libs/libnuma.so: undefined reference to `major'
collect2: error: ld returned 1 exit status
This was fixed in upstream commit:
https://github.com/numactl/numactl/commit/25691a084a2012a339395ade567dbae814e237e9
The fix is available in v2.0.13.
Signed-off-by: Ali Alnubani <alialnu@mellanox.com>
---
doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst b/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst
index e799b0ba4..e47218af9 100644
--- a/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst
+++ b/doc/guides/linux_gsg/cross_build_dpdk_for_arm64.rst
@@ -50,7 +50,7 @@ NUMA is required by most modern machines, not needed for non-NUMA architectures.
git clone https://github.com/numactl/numactl.git
cd numactl
- git checkout v2.0.11 -b v2.0.11
+ git checkout v2.0.13 -b v2.0.13
./autogen.sh
autoconf -i
./configure --host=aarch64-linux-gnu CC=aarch64-linux-gnu-gcc --prefix=<numa install dir>
--
2.24.0
next reply other threads:[~2019-11-27 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 15:23 Ali Alnubani [this message]
2019-11-28 2:10 ` Ruifeng Wang (Arm Technology China)
2019-11-28 2:30 ` Gavin Hu (Arm Technology China)
2019-11-28 19:01 ` Thomas Monjalon
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=20191127152259.29424-1-alialnu@mellanox.com \
--to=alialnu@mellanox.com \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=joyce.kong@arm.com \
--cc=ruifeng.wang@arm.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).