From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/meson Bug 1787] ARM toolchin prefix changed in newest toolchain
Date: Fri, 12 Sep 2025 09:28:53 +0000 [thread overview]
Message-ID: <bug-1787-3@https.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1787
Bug ID: 1787
Summary: ARM toolchin prefix changed in newest toolchain
Product: DPDK
Version: 24.11
Hardware: ARM
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: meson
Assignee: dev@dpdk.org
Reporter: nelio.laranjeiro@6wind.com
Target Milestone: ---
In config/arm/* files in the binary section, the prefix tool chain is hardcoded
with the old notation i.e. arch-os-abi, this has changed to arch-vendor-os-abi
causing all this files unusable with latest tool chain.
Example: arm-gnu-toolchain-14.3.rel1-aarch64-aarch64-none-linux-gnu.tar.xz [1]
which prefix is: aarch64-none-linux-gnu instead of old prefix
aarch64-linux-gnu.
[1]
https://developer.arm.com/-/media/Files/downloads/gnu/14.3.rel1/binrel/arm-gnu-toolchain-14.3.rel1-aarch64-aarch64-none-linux-gnu.tar.xz
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3102 bytes --]
reply other threads:[~2025-09-12 9:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-1787-3@https.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.