DPDK usage discussions
 help / color / mirror / Atom feed
From: Mark de Roussier <mark@hitomi-broadcast.tv>
To: David Marchand <david.marchand@redhat.com>
Cc: "Дмитрий Степанов" <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 16:12:10 +0000	[thread overview]
Message-ID: <LO3P123MB328937147A99C4EA1874E6748F8E9@LO3P123MB3289.GBRP123.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAJFAV8wjTZWjUGMWagweqpf9N6PMWeveKxb6otbLDx4_TCXLNg@mail.gmail.com>


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

>then maybe you did not reconfigure your build env.
>$ meson --reconfigure <build_dir>

🙂. I tried many meson commands to wipe/reconfigure my build environment, but I've just blown away the whole build directory and started again, and now it appears to be working ( though I thought I'd tried that before too ). Maybe I missed a trick with reconfiguring meson, I don't know. The PC has also been restarted a few times. The ninja build succeeds ( with warnings ).

Anyway, I'm encouraged that there are people listening out there, and willing to try helping  🙂.

Thanks folk,
Mark


[cid:a8ca81a5-8baf-4da6-a3b6-bd53d0013478][cid:4721cdc2-3222-4b8f-8ce2-87d22690b4f8]
________________________________
From: David Marchand <david.marchand@redhat.com>
Sent: 20 July 2022 16:18
To: Mark de Roussier <mark@hitomi-broadcast.tv>
Cc: Дмитрий Степанов <stepanov.dmit@gmail.com>; users@dpdk.org <users@dpdk.org>
Subject: Re: Couple of build problems ( Fedora 36, DPDK 21.11.1 )

On Wed, Jul 20, 2022 at 4:59 PM Mark de Roussier
<mark@hitomi-broadcast.tv> wrote:
>
> Hello David,
>
> 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.

Well, that's what I have on my Fedora to build mlx drivers.

Btw, librte_common_mlx5 is an internal DPDK driver.
If you still see that this component is disabled after installing
those headers via the devel packages, then maybe you did not
reconfigure your build env.
$ meson --reconfigure <build_dir>


If this is not working, you'll have to look into
<build_dir>/meson-logs/, there may be some useful info in those logs.


--
David Marchand


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

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

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

  reply	other threads:[~2022-07-20 16:12 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 [this message]
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=LO3P123MB328937147A99C4EA1874E6748F8E9@LO3P123MB3289.GBRP123.PROD.OUTLOOK.COM \
    --to=mark@hitomi-broadcast.tv \
    --cc=david.marchand@redhat.com \
    --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).