From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org,
Wathsala Vithanage <wathsala.vithanage@arm.com>
Subject: Re: [PATCH] config/arm: fix 32-bit cross compile with latest GCC
Date: Wed, 28 Jan 2026 10:56:57 +0100 [thread overview]
Message-ID: <2619339.Sgy9Pd6rRy@thomas> (raw)
In-Reply-To: <63f59ea1-983c-48b2-a502-c6546f149a1e@arm.com>
14/01/2026 18:37, Wathsala Vithanage:
>
> On 1/14/26 11:13, Bruce Richardson wrote:
> > 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>
>
> Reviewed-by: Wathsala Vithanage <wathsala.vithanage@arm.com>
Applied, thanks.
prev parent reply other threads:[~2026-01-28 9:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 17:13 [PATCH] config/arm: fix 32-bit cross compile with latest GCC Bruce Richardson
2026-01-14 17:37 ` Wathsala Vithanage
2026-01-28 9:56 ` Thomas Monjalon [this message]
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=2619339.Sgy9Pd6rRy@thomas \
--to=thomas@monjalon.net \
--cc=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