From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: wathsala.vithanage@arm.com,
Bruce Richardson <bruce.richardson@intel.com>,
stable@dpdk.org
Subject: [PATCH] config/arm: fix 32-bit cross compile with latest GCC
Date: Wed, 14 Jan 2026 17:13:35 +0000 [thread overview]
Message-ID: <20260114171335.3051704-1-bruce.richardson@intel.com> (raw)
When building for 32-bit arm with GCC versions >=11 and using the
DPDK-provided cross-file, the initial configuration step fails The
error given is:
config/meson.build:189:8: ERROR: Problem encountered: \
Compiler does not support "armv8-a" arch flag.
but the real problem is actually an fpu-related error which is explained
in the meson log file:
cc1: error: '-mfloat-abi=hard': selected architecture lacks an FPU
This error can be fixed by specifying an fpu explicitly, and a number of
options will work, e.g. -mfpu=neon, -mfpu=fp-armv8. Choosing the latter
here to avoid mandating neon by default.
Fixes: e754875c296c ("config/arm: add aarch32 cross-compilation")
Cc: stable@dpdk.org
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
This patch should fix errors seen in the CI when building for 32-bit arm
on Ubuntu 24.04 and later. CI systems running older Ubuntu using GCC 9
do not show this error, which is why it hasn't been an issue till
recently.
---
config/arm/arm32_armv8_linux_gcc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/config/arm/arm32_armv8_linux_gcc b/config/arm/arm32_armv8_linux_gcc
index abcb182b16..231c9ac7a7 100644
--- a/config/arm/arm32_armv8_linux_gcc
+++ b/config/arm/arm32_armv8_linux_gcc
@@ -13,5 +13,8 @@ cpu_family = 'aarch32'
cpu = 'armv8-a'
endian = 'little'
+[built-in options]
+c_args = '-mfpu=fp-armv8'
+
[properties]
platform = 'generic_aarch32'
--
2.51.0
next reply other threads:[~2026-01-14 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 17:13 Bruce Richardson [this message]
2026-01-14 17:37 ` [PATCH] config/arm: fix 32-bit cross compile with latest GCC Wathsala Vithanage
2026-01-28 9:56 ` 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=20260114171335.3051704-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=wathsala.vithanage@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