From: Shahaf Shuler <shahafs@mellanox.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
Yongseok Koh <yskoh@mellanox.com>,
Matan Azrad <matan@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [BUG] mlx5 build failure on Debian testing
Date: Thu, 12 Jul 2018 05:49:55 +0000 [thread overview]
Message-ID: <DB7PR05MB4426FD5919E44EF0F21D0CB0C3590@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20180711140749.0d975323@xeon-e3>
Hi Stephen,
Thursday, July 12, 2018 12:08 AM, Stephen Hemminger:
> Subject: [BUG] mlx5 build failure on Debian testing
>
> I am seeing a build failure of MLX5 driver on Debian testing (buster) with
> dpdk.org master branch.
>
> This is using libibverbs-dev version 19.0-1
>
> The failure is:
> mlx5_glue.h:94:11: error: ‘struct ibv_counter_set_init_attr’ declared inside
> parameter list will not be visible outside of this definition or declaration [-
> Werror]
> struct ibv_counter_set_init_attr *init_attr);
> ^~~~~~~~~~~~~~~~~~~~~~~~~
>
> It looks like this is being caused because
> HAVE_IBV_DEVICE_COUNTERS_SET_SUPPORT is not set, but the header file
> does not have the counter stuff.
>
> The Makefile is generating this mlx5 autoconf file by looking for "enum
> IBV_FLOW_SPEC_ACTION_COUNT"
> in /usr/include/infiniband/verbs.h. This enum is present, but counters are
> not.
>
> $ grep IBV_FLOW_SPEC_ACTION /usr/include/infiniband/verbs.h
> IBV_FLOW_SPEC_ACTION_TAG = 0x1000,
> IBV_FLOW_SPEC_ACTION_DROP = 0x1001,
> IBV_FLOW_SPEC_ACTION_HANDLE = 0x1002,
> IBV_FLOW_SPEC_ACTION_COUNT = 0x1003,
Thanks for reporting, this was also raised by Ferruh.
We will fix this issue. The fix is pending series [1] as it changes the entire flow engine.
[1]
https://patches.dpdk.org/project/dpdk/list/?series=512
prev parent reply other threads:[~2018-07-12 5:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 21:07 Stephen Hemminger
2018-07-12 5:49 ` Shahaf Shuler [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=DB7PR05MB4426FD5919E44EF0F21D0CB0C3590@DB7PR05MB4426.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=stephen@networkplumber.org \
--cc=yskoh@mellanox.com \
/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).