From: Stephen Hemminger <stephen@networkplumber.org>
To: Chinmaya Agarwal <Chinmaya.Agarwal@hsc.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Error while compiling DPDK with VPP 23.02
Date: Wed, 26 Apr 2023 16:33:18 -0700 [thread overview]
Message-ID: <20230426163318.516c8abd@hermes.local> (raw)
In-Reply-To: <PN3PR01MB577040C683536AC5A45BF67B94659@PN3PR01MB5770.INDPRD01.PROD.OUTLOOK.COM>
On Wed, 26 Apr 2023 08:03:43 +0000
Chinmaya Agarwal <Chinmaya.Agarwal@hsc.com> wrote:
> Hi,
>
> While compiling DPDK for VPP v23.02 on Centos 8, we saw below compilation error:-
>
> In file included from ../src-dpdk/drivers/common/mlx5/mlx5_common_mr.c:14:
> ../src-dpdk/drivers/common/mlx5/linux/mlx5_glue.h:15:10: fatal error: infiniband/mlx5dv.h: No such file or directory
> #include <infiniband/mlx5dv.h>
> ^~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
> ninja: build stopped: subcommand failed.
> Could not rebuild .
> make[3]: *** [packages/dpdk.mk:218: /opt/vpp/build/external/rpm/tmp/.dpdk.install.ok] Error 255
> make[3]: Leaving directory '/opt/vpp/build/external'
> error: Bad exit status from /var/tmp/rpm-tmp.whpNsT (%install)
>
>
> RPM build errors:
> Bad exit status from /var/tmp/rpm-tmp.whpNsT (%install)
> make[2]: *** [Makefile:113: vpp-ext-deps-23.02-8.x86_64.rpm] Error 1
> make[2]: Leaving directory '/opt/vpp/build/external'
> make[1]: *** [Makefile:125: install-rpm] Error 2
> make[1]: Leaving directory '/opt/vpp/build/external'
> make: *** [Makefile:627: install-ext-deps] Error 2
>
> It is not able to find "infiniband/mlx5dv.h".
>
> What could be the reason for this error? Any package that might be missing and needs to install or are we missing something here?
>
Probably same package requirements as normal DPDK support for Mellanox.
https://doc.dpdk.org/guides/platform/mlx5.html#mlx5-common-compilation
prev parent reply other threads:[~2023-04-26 23:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 8:03 Chinmaya Agarwal
2023-04-26 23:33 ` Stephen Hemminger [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=20230426163318.516c8abd@hermes.local \
--to=stephen@networkplumber.org \
--cc=Chinmaya.Agarwal@hsc.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).