From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [lab/job scripts Bug 1532] Windows Server 2022 misses the Mlx5DevX library installation
Date: Thu, 05 Sep 2024 05:11:44 +0000 [thread overview]
Message-ID: <bug-1532-149@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1532
Bug ID: 1532
Summary: Windows Server 2022 misses the Mlx5DevX library
installation
Product: lab
Version: unspecified
Hardware: x86
OS: Windows
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: job scripts
Assignee: ci@dpdk.org
Reporter: adham@nvidia.com
CC: dpdklab@iol.unh.edu
Target Milestone: ---
While reviewing the tests that are running on the uploaded patches, one of our
team found that the compilation of the dpdk is ignoring the MLX5 as the
Mlx5Devx.h is missing.
common/mlx5: missing dependency, "mlx5devx.h"
Ref patch: https://lab.dpdk.org/results/dashboard/patchsets/30758/
Most likely that the upgrade from Windows server 2019 to 2022, missed the
installation of the Devx_SDK, that can be installed as a component from the
Nvidia WinOF-2 package that can be found here:
https://network.nvidia.com/products/adapter-software/ethernet/windows/winof-2/
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3313 bytes --]
reply other threads:[~2024-09-05 5:11 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-1532-149@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=ci@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).