From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/meson Bug 1703] meson: Unsupported part number for ARM Grace during meson setup
Date: Tue, 29 Apr 2025 02:38:40 +0000 [thread overview]
Message-ID: <bug-1703-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1616 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1703
Bug ID: 1703
Summary: meson: Unsupported part number for ARM Grace during
meson setup
Product: DPDK
Version: 22.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: minor
Priority: Normal
Component: meson
Assignee: dev@dpdk.org
Reporter: probb@iol.unh.edu
Target Milestone: ---
Created attachment 313
--> https://bugs.dpdk.org/attachment.cgi?id=313&action=edit
meson log
Hello. I am seeing an error reported by meson when attempting to run meson
setup on 22.11.
steps to reproduce:
1. clone dpdk-stable and checkout to 22.11
2. run "meson setup build"
error:
Message: Arm implementer: Arm
Message: Arm part number: 0xd4f
config/arm/meson.build:603:8: ERROR: Problem encountered: Unsupported part
number 0xd4f of implementer 0x41. Please add support for it or use the generic
(-Dplatform=generic) build.
System info:
DPDK version: 22.11
OS: Ubuntu 24.04
CPU: Vendor ID: ARM
BIOS Vendor ID: NVIDIA
Model name: Neoverse-V2
BIOS Model name: Grace A02 AOM-SCM-NV CPU @ 3.4GHz
meson version: .53 and 1.3.2 (tried both)
If you pass in -Dplatform=generic meson (and ninja) run to completion without
error. But, I imagine support for this part number should be added so that
meson will run without this flag, so I've created this ticket.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3611 bytes --]
next reply other threads:[~2025-04-29 2:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 2:38 bugzilla [this message]
[not found] <bug-1703-3@https.bugs.dpdk.org/>
2025-08-25 13:35 ` [DPDK/meson Bug 1703] meson: Unsupported part number for ARM Grace during meson setup bugzilla
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=bug-1703-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.