DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andre Muezerie <andremue@linux.microsoft.com>
Cc: dev@dpdk.org, Andre Muezerie <andremue@linux.microsoft.com>
Subject: [PATCH 0/1] unresolved symbol mlx5_geneve_tlv_parser_create
Date: Mon,  5 May 2025 07:45:36 -0700	[thread overview]
Message-ID: <1746456337-6278-1-git-send-email-andremue@linux.microsoft.com> (raw)

When compiling DPDK with mlx5 using clang on Windows with
"debug" buildtype the error below is hit:

net_mlx5_mlx5_flow_dv.c.obj : error LNK2019: unresolved external symbol
    mlx5_geneve_tlv_parser_create referenced in function
    flow_dv_discover_priorities
drivers\rte_net_mlx5-25.dll : fatal error LNK1120: 1 unresolved externals

With a "release" buildtype the error is not seen, which explains why this
issue was not reported earlier.

The same problem will show up with MSVC, but patches which are still under
review are needed for this to be hit with MSVC.

The cause of this problem seems to be that mlx5_flow_geneve.c is only
compiled on Linux. This patch fixes the issue by compiling the file on all
operating systems. It also sorts the file names in meson.build in
alphabetical order.


REPRO STEPS (On Windows)

set DEVX_INC_PATH=V:\soft\MLNX_WinOF2_DevX_SDK\inc
set DEVX_LIB_PATH=V:\soft\MLNX_WinOF2_DevX_SDK\lib
set CFLAGS=-I"%DEVX_INC_PATH%"
set LDFLAGS=-Wl,-LIBPATH:"%DEVX_LIB_PATH%"
set CC=clang
meson setup -Dexamples=helloworld build --buildtype debug
ninja -C build


Andre Muezerie (1):
  net/mlx5: unresolved symbol mlx5_geneve_tlv_parser_create

 drivers/net/mlx5/meson.build | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

--
2.49.0.vfs.0.0


             reply	other threads:[~2025-05-05 14:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-05 14:45 Andre Muezerie [this message]
2025-05-05 14:45 ` [PATCH 1/1] net/mlx5: " Andre Muezerie

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=1746456337-6278-1-git-send-email-andremue@linux.microsoft.com \
    --to=andremue@linux.microsoft.com \
    --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).