DPDK usage discussions
 help / color / mirror / Atom feed
From: "Дмитрий Степанов" <stepanov.dmit@gmail.com>
To: Mark de Roussier <mark@hitomi-broadcast.tv>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: Couple of build problems ( Fedora 36, DPDK 21.11.1 )
Date: Wed, 20 Jul 2022 12:55:25 +0300	[thread overview]
Message-ID: <CA+-SuJ3wgsTE5kC8jsdE2oy+3oMTzELtsBTHAbytGoq4JxeEqg@mail.gmail.com> (raw)
In-Reply-To: <LO3P123MB3289F3AFEB8D18E6F408F0188F8E9@LO3P123MB3289.GBRP123.PROD.OUTLOOK.COM>


[-- Attachment #1.1: Type: text/plain, Size: 3948 bytes --]

Hey!
According to missing mlx5 dependency - i have the same problem on my Ubuntu
system.
You should check full meson build error logs.
In my case the error was in missing libmlx5 library

> Run-time dependency libmlx5 found: NO (tried pkgconfig)

Installing the libibverbs-dev package resolved the issue!

ср, 20 июл. 2022 г. в 11:38, Mark de Roussier <mark@hitomi-broadcast.tv>:

> Hi folk,
>
> I'm just starting to experiment with DPDK, but I'm noticing some build
> issues. I'm using Fedora 36, and DPDK 21.11.1, and following the build
> instructions at https://core.dpdk.org/doc/quick-start/, building all
> examples ( meson -Dexamples=all build ).
>
> The first problem is that the build is not finding certain libraries which
> are installed and known about by pkg-config.
>
> >[mderouss@mark-dt ~]$ pkg-config --modversion jansson
> >2.13.1
> >[mderouss@mark-dt ~]$ pkg-config --modversion numa
> >2.0.14
> >[mderouss@mark-dt ~]$ pkg-config --modversion libarchive
> >3.5.3
>
> However, using LIBRARY_PATH to specify their location appears to resolve
> the problem. There is a potentially relevant error in the meson log :
>
>     [Errno 21] Is a directory:
> '/home/mderouss/Projects/dpdk/dpdk-stable-21.11.1/buildtools/pkg-config'
>     Unusable script
> '/home/mderouss/Projects/dpdk/dpdk-stable-21.11.1/buildtools/pkg-config'
>     Program pkg-config found: YES (/usr/bin/pkg-config)
>
> Is this expected behaviour, i.e. LIBRARY_PATH is expected to be set ?
>
> The more taxing problem is that I am using ( for this experiment ) a
> Mellanox NIC :
>
> >[mderouss@mark-dt ~]$ lspci | grep Mellanox
> >06:00.0 Ethernet controller: Mellanox Technologies MT27710 Family
> [ConnectX-4 Lx]
> >06:00.1 Ethernet controller: Mellanox Technologies MT27710 Family
> [ConnectX-4 Lx]
>
> The meson log reports missing dependencies. It isn't clear to me how I am
> supposed to satisfy the unresolved dependencies with respect to Mellanox
> related libraries, in particular the 'missing internal dependency' ? The
> meson log reports the following, but I think I'm only interested in the mlx
> ones :
>
>     drivers:
>    common/mvep: missing dependency, "libmusdk"
>    *common/mlx5: missing dependency, "mlx5"*
>    *net/mlx4: missing dependency, "mlx4"*
>    *net/mlx5: missing internal dependency, "common_mlx5"*
>    net/mvneta: missing dependency, "libmusdk"
>    net/mvpp2: missing dependency, "libmusdk"
>    net/nfb: missing dependency, "libnfb"
>    raw/ioat: replaced by dmadev drivers
>    crypto/armv8: missing dependency, "libAArch64crypto"
>    *crypto/mlx5: missing internal dependency, "common_mlx5"*
>    crypto/mvsam: missing dependency, "libmusdk"
>    compress/isal: missing dependency, "libisal"
>    *compress/mlx5: missing internal dependency, "common_mlx5"*
>   * regex/mlx5: missing internal dependency, "common_mlx5"*
>    *vdpa/mlx5: missing internal dependency, "common_mlx5"*
>    gpu/cuda: missing dependency, "cuda.h"
>
> I read DPDK documentation which seems to suggest that support for Mellanox
> NICs is somehow 'built in' to DPDK, but this does not appear to be the case
> ?
>
> The documentation refers to a library 'librte_common_mlx5', but does not
> explain where this can be found. I've looked at downloads from NVIDIA, but
> even so I am not clear what I need. I've installed the 'RDMA Core Userspace
> Library' in my system as they are available from the distro, but I'm not
> sure if these are even relevant :
>
> >[mderouss@mark-dt ~]$ pkg-config --list-all | grep mlx
> >libmlx4                        libmlx4 - RDMA Core Userspace Library
> >libmlx5                        libmlx5 - RDMA Core Userspace Library
>
> Could someone possibly clarify what I actually need, and where I should
> get it from ?
>
> Regards,
> Mark de Roussier
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

[-- Attachment #1.2: Type: text/html, Size: 8564 bytes --]

[-- Attachment #2: Outlook-m5klsbya.jpg --]
[-- Type: image/jpeg, Size: 40880 bytes --]

[-- Attachment #3: Outlook-gak3b304.jpg --]
[-- Type: image/jpeg, Size: 22705 bytes --]

  reply	other threads:[~2022-07-20  9:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-20  8:38 Mark de Roussier
2022-07-20  9:55 ` Дмитрий Степанов [this message]
2022-07-20 12:19   ` Mark de Roussier
2022-07-20 14:14     ` David Marchand
2022-07-20 14:58       ` Mark de Roussier
2022-07-20 15:18         ` David Marchand
2022-07-20 16:12           ` Mark de Roussier
2022-07-20 16:25             ` David Marchand
2022-07-20 15:37         ` Dmitry Kozlyuk

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=CA+-SuJ3wgsTE5kC8jsdE2oy+3oMTzELtsBTHAbytGoq4JxeEqg@mail.gmail.com \
    --to=stepanov.dmit@gmail.com \
    --cc=mark@hitomi-broadcast.tv \
    --cc=users@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).