From: Ali Alnubani <alialnu@mellanox.com>
To: dev@dpdk.org
Cc: jerinj@marvell.com, pbhagavatula@marvell.com, stable@dpdk.org
Subject: [dpdk-stable] [PATCH 2/2] mk: disable OcteonTx2 on old compilers
Date: Mon, 28 Oct 2019 13:25:35 +0200 [thread overview]
Message-ID: <20191028112535.692-2-alialnu@mellanox.com> (raw)
In-Reply-To: <20191028112535.692-1-alialnu@mellanox.com>
This disables OcteonTx2 for gcc 4.8.5 as the compiler is
emitting "internal compiler error" for aarch64.
Fixes: 9a8864c8b5da ("net/octeontx2: add build and doc infrastructure")
Cc: stable@dpdk.org
Signed-off-by: Ali Alnubani <alialnu@mellanox.com>
---
mk/toolchain/gcc/rte.toolchain-compat.mk | 3 +++
1 file changed, 3 insertions(+)
diff --git a/mk/toolchain/gcc/rte.toolchain-compat.mk b/mk/toolchain/gcc/rte.toolchain-compat.mk
index 00d6fd642..dd2c4e5da 100644
--- a/mk/toolchain/gcc/rte.toolchain-compat.mk
+++ b/mk/toolchain/gcc/rte.toolchain-compat.mk
@@ -104,6 +104,9 @@ else
CONFIG_RTE_LIBRTE_PMD_OCTEONTX_SSOVF=d
CONFIG_RTE_LIBRTE_OCTEONTX_MEMPOOL=d
CONFIG_RTE_LIBRTE_OCTEONTX_PMD=d
+ CONFIG_RTE_LIBRTE_PMD_OCTEONTX2_EVENTDEV=d
+ CONFIG_RTE_LIBRTE_OCTEONTX2_MEMPOOL=d
+ CONFIG_RTE_LIBRTE_OCTEONTX2_PMD=d
endif
endif
--
2.23.0
next prev parent reply other threads:[~2019-10-28 11:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 11:25 [dpdk-stable] [PATCH 1/2] mk: fix build on arm64 Ali Alnubani
2019-10-28 11:25 ` Ali Alnubani [this message]
2019-10-30 11:49 ` [dpdk-stable] [dpdk-dev] [PATCH 2/2] mk: disable OcteonTx2 on old compilers Jerin Jacob
2019-10-28 16:34 ` [dpdk-stable] [dpdk-dev] [PATCH 1/2] mk: fix build on arm64 Thomas Monjalon
2019-10-30 11:42 ` Jerin Jacob
2019-11-04 13:30 ` [dpdk-stable] [PATCH v2 " Ali Alnubani
2019-11-04 13:30 ` [dpdk-stable] [PATCH v2 2/2] mk: disable OCTEON TX2 on old compilers Ali Alnubani
2019-11-08 15:32 ` 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=20191028112535.692-2-alialnu@mellanox.com \
--to=alialnu@mellanox.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=stable@dpdk.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).