DPDK usage discussions
 help / color / mirror / Atom feed
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Mark de Roussier <mark@hitomi-broadcast.tv>
Cc: "David Marchand" <david.marchand@redhat.com>,
	"Дмитрий Степанов" <stepanov.dmit@gmail.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: Couple of build problems ( Fedora 36, DPDK 21.11.1 )
Date: Wed, 20 Jul 2022 18:37:17 +0300	[thread overview]
Message-ID: <20220720183717.343b2222@sovereign> (raw)
In-Reply-To: <LO3P123MB3289D940DE1C43ABBC600BB08F8E9@LO3P123MB3289.GBRP123.PROD.OUTLOOK.COM>

2022-07-20 14:58 (UTC+0000), Mark de Roussier:
> thanks for the idea, but I'm afraid that's not the case. I do have that already, that is what is providing libmlx4 and libmlx5. But it does not contain librte_common_mlx5, which is what I think is probably the source of my problem.

librte_common_mlx5 is built as part of DPDK.
The dependency chain is as follows ("|" denotes DPDK boundary):

librte_{net,...}_mlx5 -> librte_common_mlx5 -> | -> libmlx5, libibverbs

I think the root cause is with pkg-config, as described in your first message.
pkg-config is used to find libraries, including libibverbs and libmlx5.
librte_common_mlx5 build is skipped if they are not found.

This message is harmless:

[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'

LIBRARY_PATH should not be needed.
What is the full build log?

      parent reply	other threads:[~2022-07-20 15:37 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 ` Дмитрий Степанов
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 [this message]

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=20220720183717.343b2222@sovereign \
    --to=dmitry.kozliuk@gmail.com \
    --cc=david.marchand@redhat.com \
    --cc=mark@hitomi-broadcast.tv \
    --cc=stepanov.dmit@gmail.com \
    --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).