DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1798] Meson can't find MLX5 build dependencies with clang
Date: Fri, 03 Oct 2025 11:45:34 +0000	[thread overview]
Message-ID: <bug-1798-3@http.bugs.dpdk.org/> (raw)

http://bugs.dpdk.org/show_bug.cgi?id=1798

            Bug ID: 1798
           Summary: Meson can't find MLX5 build dependencies with clang
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: alialnu@nvidia.com
  Target Milestone: ---

Created attachment 331
  --> http://bugs.dpdk.org/attachment.cgi?id=331&action=edit
Meson logs with and without the first bad commit

MLX5 drivers are getting disabled due to missing dependency warnings:

Message: Disabling mlx5 [drivers/net/mlx5]: missing internal dependency
"common_mlx5"

Build command:
CC=clang PKG_CONFIG_PATH=/opt/rdma-core/build/lib/pkgconfig meson
--werror --buildtype=debugoptimized build

OS: Ubuntu 22.04
Compiler: clang 14.0.0
Meson: 0.61.2

gcc does not reproduce.

$ PKG_CONFIG_PATH=:/opt/rdma-core/build/lib/pkgconfig pkg-config --modversion
libibverbs
1.15.60.0

git-bisect points to 0681e15f42df ("build: validate libraries returned from
meson find function").

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2025-10-03 11:45 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-1798-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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).