From: Cliff Burdick <shaklee3@gmail.com>
To: ahart@domainhart.com
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] Problems compiling DPDK for MLX4
Date: Thu, 11 Oct 2018 12:11:01 -0700 [thread overview]
Message-ID: <CA+Gp1nbK0qw+w1Jw36Axrg-znc21UCqPCWquiBCmS7Vhi3i4TA@mail.gmail.com> (raw)
In-Reply-To: <FDECF8E4-D881-46B8-82BE-8F3D6ADD6969@domainhart.com>
The easy workaround is to install the mellanox OFED package with the flags
--dpdk --upstream-libs.
On Thu, Oct 11, 2018 at 8:57 AM Anthony Hart <ahart@domainhart.com> wrote:
>
> Having problems compiling DPDK for the Mellanox PMD.
>
> For dpdk-18-08 I get...
>
> CC efx_phy.o
> In file included from /root/th/dpdk-18.08/drivers/net/mlx4/mlx4_txq.c:35:0:
> /root/th/dpdk-18.08/drivers/net/mlx4/mlx4_glue.h:16:31: fatal error:
> infiniband/mlx4dv.h: No such file or directory
> #include <infiniband/mlx4dv.h>
> ^
> compilation terminated.
> In file included from
> /root/th/dpdk-18.08/drivers/net/mlx4/mlx4_intr.c:32:0:
> /root/th/dpdk-18.08/drivers/net/mlx4/mlx4_glue.h:16:31: fatal error:
> infiniband/mlx4dv.h: No such file or directory
> #include <infiniband/mlx4dv.h>
>
>
> For dpdk-1711.3
>
> CC mlx5.o
> /root/th/dpdk-stable-17.11.3/drivers/net/mlx5/mlx5.c: In function
> ‘mlx5_pci_probe’:
> /root/th/dpdk-stable-17.11.3/drivers/net/mlx5/mlx5.c:921:21: error:
> ‘struct ibv_device_attr_ex’ has no member named ‘device_cap_flags_ex’
> !!(device_attr_ex.device_cap_flags_ex &
> ^
> /root/th/dpdk-stable-17.11.3/drivers/net/mlx5/mlx5.c:922:7: error:
> ‘IBV_DEVICE_RAW_IP_CSUM’ undeclared (first use in this function)
> IBV_DEVICE_RAW_IP_CSUM);
> ^
> /root/th/dpdk-stable-17.11.3/drivers/net/mlx5/mlx5.c:922:7: note: each
> undeclared identifier is reported only once for each function it appears in
> /root/th/dpdk-stable-17.11.3/drivers/net/mlx5/mlx5.c:942:18: error:
> ‘struct ibv_device_attr_ex’ has no member named ‘rss_caps’
> device_attr_ex.rss_caps.max_rwq_indirection_table_size;
> ^
>
>
> This is on Lentos 7.5 (3.10.0-862.14.4.el7.x86_64)
>
> With mlnx-en-4.4-1.0.1.0-rhel7.5-x86_64.iso installed
>
>
> Any thoughts?
>
> thanks
> —
> tony
>
>
>
next prev parent reply other threads:[~2018-10-11 19:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 15:57 Anthony Hart
2018-10-11 19:11 ` Cliff Burdick [this message]
2018-10-11 20:12 ` Stephen Hemminger
2018-10-11 20:21 ` Anthony Hart
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+Gp1nbK0qw+w1Jw36Axrg-znc21UCqPCWquiBCmS7Vhi3i4TA@mail.gmail.com \
--to=shaklee3@gmail.com \
--cc=ahart@domainhart.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).