From: Thomas Monjalon <thomas@monjalon.net>
To: Patrick Robb <probb@iol.unh.edu>
Cc: David Marchand <david.marchand@redhat.com>,
dev@dpdk.org, andremue@linux.microsoft.com,
Dariusz Sosnowski <dsosnowski@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
Tal Shnaiderman <talshn@nvidia.com>,
Tyler Retzlaff <roretzla@linux.microsoft.com>,
Manit Mahajan <mmahajan@iol.unh.edu>
Subject: Re: [PATCH] common/mlx5: fix dependency detection on Windows
Date: Mon, 16 Jun 2025 09:35:23 +0200 [thread overview]
Message-ID: <5837335.VQhiAETyHQ@thomas> (raw)
In-Reply-To: <CAJvnSUD8aW-y_qdLN_GnRQfUns9H2QZcbKjg3TtauRXJ4Ojx4g@mail.gmail.com>
This is the documentation to prepare mlx5 on Windows:
https://docs.nvidia.com/networking/display/winof2v290/devx+interface
13/06/2025 23:48, Patrick Robb:
> Good catch David on this system having a partial install of mlx5dev
> header/library.
>
> NVIDIA guys, do any of you have a link to the current install procedure or
> package? If not I can probably find whatever is correct. Thanks.
>
> Either way we'll update devx on the Windows system Monday - thanks for your
> patience.
>
> On Fri, Jun 13, 2025 at 5:42 AM David Marchand <david.marchand@redhat.com>
> wrote:
>
> > On Fri, Jun 13, 2025 at 10:10 AM David Marchand
> > <david.marchand@redhat.com> wrote:
> > >
> > > Don't *require* mlx5dev library when testing its presence.
> >
> > For the record, this was seen in a UNH env that seems to have
> > partially installed mlx5 dependencies.
> >
> > Has header "mlx5devx.h" : YES
> > drivers\common\mlx5\windows\meson.build:10:0: ERROR: C shared or
> > static library 'mlx5devx' not found
> >
> > >
> > > Fixes: 85c51a4ffab8 ("common/mlx5: get Windows dependency from standard
> > variables")
> > >
> > > Signed-off-by: David Marchand <david.marchand@redhat.com>
next prev parent reply other threads:[~2025-06-16 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 8:10 David Marchand
2025-06-13 9:42 ` David Marchand
2025-06-13 21:48 ` Patrick Robb
2025-06-16 7:35 ` Thomas Monjalon [this message]
2025-06-18 9:42 ` David Marchand
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=5837335.VQhiAETyHQ@thomas \
--to=thomas@monjalon.net \
--cc=andremue@linux.microsoft.com \
--cc=bingz@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=mmahajan@iol.unh.edu \
--cc=orika@nvidia.com \
--cc=probb@iol.unh.edu \
--cc=roretzla@linux.microsoft.com \
--cc=suanmingm@nvidia.com \
--cc=talshn@nvidia.com \
--cc=viacheslavo@nvidia.com \
/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).