From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/meson Bug 1749] Ninja Build Error on Intel CPU
Date: Mon, 07 Jul 2025 19:03:33 +0000 [thread overview]
Message-ID: <bug-1749-3@https.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1470 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1749
Bug ID: 1749
Summary: Ninja Build Error on Intel CPU
Product: DPDK
Version: 25.03
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: meson
Assignee: dev@dpdk.org
Reporter: mmahajan@iol.unh.edu
Target Milestone: ---
Hello,
A committed change to DPDK has introduced a build failure. The patch that
introduced the issue is: "net/intel: generalize vectorized Rx rearm" (commit
ID: c70e8654a81315e33d84f5d972174c9547b941c4). It was authored by Anatoly
Burakov and merged into dpdk on 2025-06-27.
An earlier patch in the series (net/ice: rename 16-byte descriptor flag)
renames the ICE driver Dc_arg from DRTE_LIBRTE_ICE_16BYTE_RX_DESC to
DRTE_NET_INTEL_USE_16BYTE_DESC. And when using this new flag in the meson
setup, it causes the build to fail.
Build commands:
CC=gcc meson -Denable_kmods=True -Dlibdir=lib
-Dc_args='-DRTE_NET_INTEL_USE_16BYTE_DESC' --default-library=static
x86_64-native-linux-gcc
ninja -C x86_64-native-linux-gcc
OS: Ubuntu VERSION="22.04.3 LTS (Jammy Jellyfish)"
GCC: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Meson: 1.3.1
CPU INFO
--------
Arch: x86_64
Model name: Intel(R) Xeon(R) Platinum 8360Y CPU @ 2.40GHz
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3352 bytes --]
reply other threads:[~2025-07-07 19:03 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-1749-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 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).