patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ali Alnubani <>
Subject: [dpdk-stable] [PATCH 1/2] mk: fix build on arm64
Date: Mon, 28 Oct 2019 13:25:34 +0200	[thread overview]
Message-ID: <> (raw)

OcteonTx was disabled for causing an internal compiler error on old gcc
See commit 4f760550a093 ("mk: disable OcteonTx for buggy compilers").

The condition that was added later to apply disabling OcteonTx
only on arm64 caused the condition to never be obeyed because it
compares ["arm64"] to [arm64].

This fixes the condition by using RTE_ARCH instead of CONFIG_RTE_ARCH,
because the former has the quotes removed, while the later doesn't.

Fixes: f3af3e44a444 ("mk: disable OcteonTx for buggy compilers only on arm64")

Signed-off-by: Ali Alnubani <>
 mk/toolchain/gcc/ | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mk/toolchain/gcc/ b/mk/toolchain/gcc/
index ea40a11c0..00d6fd642 100644
--- a/mk/toolchain/gcc/
+++ b/mk/toolchain/gcc/
@@ -99,7 +99,7 @@ else
 	# Disable octeontx event PMD for gcc < 4.8.6 & ARCH=arm64
-	ifeq ($(CONFIG_RTE_ARCH), arm64)
+	ifeq ($(RTE_ARCH), arm64)
 	ifeq ($(shell test $(GCC_VERSION)$(GCC_PATCHLEVEL) -lt 486 && echo 1), 1)

             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 Ali Alnubani [this message]
2019-10-28 11:25 ` [dpdk-stable] [PATCH 2/2] mk: disable OcteonTx2 on old compilers Ali Alnubani
2019-10-30 11:49   ` [dpdk-stable] [dpdk-dev] " 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).