From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: 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>, <dev@dpdk.org>
Subject: Re: [PATCH] doc: update parameters to use for mlx5 on Windows
Date: Wed, 16 Jul 2025 11:59:38 +0200 [thread overview]
Message-ID: <20250716095938.iqx7zjb4jcsabqas@ds-vm-debian.local> (raw)
In-Reply-To: <20250715135725.GA21424@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
On Tue, Jul 15, 2025 at 06:57:25AM -0700, Andre Muezerie wrote:
> On Tue, Jul 15, 2025 at 02:03:45PM +0200, Dariusz Sosnowski wrote:
*snip*
> > Shouldn't clang linker parameters stay as it was previously i.e., "-L..."?
>
> Not on Windows. It can be confirmed by looking at build\meson-logs\meson-log.txt,
> where it can be seen that the -L option ends up being ignored:
>
> Sanity check compiler command line: clang sanitycheckc.c -o sanitycheckc.exe -IV:\soft\MLNX_WinOF2_DevX_SDK\inc -D_FILE_OFFSET_BITS=64 -Wl,-LV:\soft\MLNX_WinOF2_DevX_SDK\lib
> Sanity check compile stdout:
> LINK : warning LNK4044: unrecognized option '/LV:\soft\MLNX_WinOF2_DevX_SDK\lib'; ignored
>
> As a result the lib mlx5devx is not found:
>
> Has header "mlx5devx.h" : YES
> Library mlx5devx found: NO
In our local Windows builds with clang providing LDFLAGS="-L..." works
and mlx5devx library is reported as found.
However, only Visual Studio Build Tools are installed,
not full Visual Studio package.
It seems that either meson or clang chooses lld, instead of MS linker.
I'll verify what happens there and let you know.
*snip*
next prev parent reply other threads:[~2025-07-16 10:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 15:22 Andre Muezerie
2025-07-15 12:03 ` Dariusz Sosnowski
2025-07-15 13:57 ` Andre Muezerie
2025-07-16 9:59 ` Dariusz Sosnowski [this message]
2025-07-15 14:14 ` [PATCH v2] " Andre Muezerie
2025-07-15 18:47 ` Patrick Robb
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=20250716095938.iqx7zjb4jcsabqas@ds-vm-debian.local \
--to=dsosnowski@nvidia.com \
--cc=andremue@linux.microsoft.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=suanmingm@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).