From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [Bug 1174] Adding compilation flags to continue compiling mlx5 in iol-x86_64-unit-testing over Windows/clang
Date: Wed, 08 Mar 2023 10:58:23 +0000 [thread overview]
Message-ID: <bug-1174-149@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1730 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1174
Bug ID: 1174
Summary: Adding compilation flags to continue compiling mlx5 in
iol-x86_64-unit-testing over Windows/clang
Product: lab
Version: unspecified
Hardware: x86
OS: Windows
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: job scripts
Assignee: ci@dpdk.org
Reporter: talshn@nvidia.com
CC: dpdklab@iol.unh.edu
Target Milestone: ---
Hi,
A community patch [1] is about to be merged to main which will change the
detection of the MLX5 DevX libraries in Windows, DPDK will no longer look for
the lib and inc folders using the env variables DEVX_INC_PATH/DEVX_LIB_PATH.
Instead the user will provide the path to those folders either in the build
command line using -Dc_args and -Dc_link_args, see example below:
-I<include_directory>
-L<library_directory>
"C:\Program Files\Meson\meson.exe" setup --buildtype debug
"-Dc_args=-I\"%DEVX_INC_PATH%\"" "-Dc_link_args=-L\"%DEVX_LIB_PATH%\"" build
Another option is to Use CFLAGS/LDFLAGS
Please change your compilations scripts in iol-x86_64-unit-testing to continue
compiling mlx5 as part of the supported PMDs on Windows by using one of the
ways stated above, not changing it will skip mlx5 as seen in the said patch CI
results on Windows/clang [2].
[1] -
https://patches.dpdk.org/project/dpdk/patch/20230302132150.3330288-2-thomas@monjalon.net/
[2] - https://lab.dpdk.org/results/dashboard/patchsets/25595/
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3947 bytes --]
next reply other threads:[~2023-03-08 10:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 10:58 bugzilla [this message]
2023-03-09 18:01 ` 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-1174-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).