From: Ali Alnubani <alialnu@mellanox.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "mchalla@marvell.com" <mchalla@marvell.com>,
"jerinj@marvell.com" <jerinj@marvell.com>
Subject: [dpdk-dev] [PATCH] mk: disable OCTEON TX2 EP on old compilers
Date: Mon, 20 Jan 2020 19:51:14 +0000 [thread overview]
Message-ID: <20200120195040.26843-1-alialnu@mellanox.com> (raw)
OCTEON TX2 isn't built for gcc 4.8.5 as the compiler emits
"internal compiler error" on aarch64. This causes the following
build error when OCTEON TX2 EP is enabled:
/usr/bin/ld: cannot find -lrte_common_octeontx2
collect2: error: ld returned 1 exit status
Fixes: 56d46d13f736 ("raw/octeontx2_ep: add build infra and device probe")
Signed-off-by: Ali Alnubani <alialnu@mellanox.com>
---
mk/toolchain/gcc/rte.toolchain-compat.mk | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/mk/toolchain/gcc/rte.toolchain-compat.mk b/mk/toolchain/gcc/rte.toolchain-compat.mk
index 7ce01a366..adf2e6eb8 100644
--- a/mk/toolchain/gcc/rte.toolchain-compat.mk
+++ b/mk/toolchain/gcc/rte.toolchain-compat.mk
@@ -102,12 +102,14 @@ else
CONFIG_RTE_LIBRTE_PMD_OPDL_EVENTDEV=d
endif
- # Disable octeontx event PMD for gcc < 4.8.6 & ARCH=arm64
+ # Disable octeontx drivers and libs for gcc < 4.8.6 & ARCH=arm64
ifeq ($(RTE_ARCH), arm64)
ifeq ($(shell test $(GCC_VERSION)$(GCC_PATCHLEVEL) -lt 486 && echo 1), 1)
CONFIG_RTE_LIBRTE_PMD_OCTEONTX_SSOVF=d
CONFIG_RTE_LIBRTE_OCTEONTX_MEMPOOL=d
CONFIG_RTE_LIBRTE_OCTEONTX_PMD=d
+
+ CONFIG_RTE_LIBRTE_PMD_OCTEONTX2_EP_RAWDEV=d
CONFIG_RTE_LIBRTE_PMD_OCTEONTX2_DMA_RAWDEV=d
CONFIG_RTE_LIBRTE_PMD_OCTEONTX2_EVENTDEV=d
CONFIG_RTE_LIBRTE_PMD_OCTEONTX2_CRYPTO=d
--
2.25.0
next reply other threads:[~2020-01-20 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 19:51 Ali Alnubani [this message]
2020-01-20 22:31 ` 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=20200120195040.26843-1-alialnu@mellanox.com \
--to=alialnu@mellanox.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mchalla@marvell.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).