From: Ruifeng Wang <ruifeng.wang@arm.com>
To: dev@dpdk.org
Cc: viktorin@rehivetech.com, bruce.richardson@intel.com,
stephen@networkplumber.org, thomas@monjalon.net,
juraj.linkes@pantheon.tech, honnappa.nagarahalli@arm.com,
nd@arm.com, stable@dpdk.org, Ruifeng Wang <ruifeng.wang@arm.com>
Subject: [PATCH v2] build: add missing arch define for Arm
Date: Mon, 17 Jan 2022 15:15:33 +0800 [thread overview]
Message-ID: <20220117071533.1221315-1-ruifeng.wang@arm.com> (raw)
In-Reply-To: <20211217085430.820773-1-ruifeng.wang@arm.com>
As per design document, RTE_ARCH is the name of the architecture.
However, the definition was missing on Arm with meson build.
It impacts applications that refers to this string.
Added for Arm builds.
Fixes: b1d48c41189a ("build: support ARM with meson")
Cc: stable@dpdk.org
Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com>
---
v2:
Renamed string for aarch32 to keep consistency with RTE_ARCH_xx defines. (Thomas)
config/arm/meson.build | 3 +++
1 file changed, 3 insertions(+)
diff --git a/config/arm/meson.build b/config/arm/meson.build
index 16e808cdd5..0066ab5f18 100644
--- a/config/arm/meson.build
+++ b/config/arm/meson.build
@@ -49,6 +49,7 @@ implementer_generic = {
['RTE_ARCH_ARM_NEON_MEMCPY', false],
['RTE_ARCH_STRICT_ALIGN', true],
['RTE_ARCH_ARMv8_AARCH32', true],
+ ['RTE_ARCH', 'armv8_aarch32'],
['RTE_CACHE_LINE_SIZE', 64]
]
}
@@ -432,11 +433,13 @@ if dpdk_conf.get('RTE_ARCH_32')
else
# armv7 build
dpdk_conf.set('RTE_ARCH_ARMv7', true)
+ dpdk_conf.set('RTE_ARCH', 'armv7')
# the minimum architecture supported, armv7-a, needs the following,
machine_args += '-mfpu=neon'
endif
else
# armv8 build
+ dpdk_conf.set('RTE_ARCH', 'arm64')
update_flags = true
soc_config = {}
if not meson.is_cross_build()
--
2.25.1
next prev parent reply other threads:[~2022-01-17 7:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 8:54 [PATCH] " Ruifeng Wang
2022-01-13 17:32 ` Thomas Monjalon
2022-01-14 9:05 ` Ruifeng Wang
2022-01-14 12:50 ` Thomas Monjalon
2022-01-17 13:12 ` Juraj Linkeš
2022-01-17 13:50 ` Morten Brørup
2022-01-19 9:44 ` Ruifeng Wang
2022-01-17 7:15 ` Ruifeng Wang [this message]
2022-01-19 9:01 ` [PATCH v2] " Thomas Monjalon
2022-01-19 9:51 ` Ruifeng Wang
2022-01-20 2:38 ` [PATCH v3] " Ruifeng Wang
2022-01-20 14:09 ` 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=20220117071533.1221315-1-ruifeng.wang@arm.com \
--to=ruifeng.wang@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=juraj.linkes@pantheon.tech \
--cc=nd@arm.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=viktorin@rehivetech.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).