From: Ali Alnubani <alialnu@mellanox.com>
To: "xiangxia.m.yue@gmail.com" <xiangxia.m.yue@gmail.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
Matan Azrad <matan@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk v1] net/mlx5: fix possible building error
Date: Sun, 1 Mar 2020 17:09:45 +0000 [thread overview]
Message-ID: <AM0PR05MB44015925E9C55C483B52FB1BD7E60@AM0PR05MB4401.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1582972040-7026-1-git-send-email-xiangxia.m.yue@gmail.com>
Hi Tonghao,
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of
> xiangxia.m.yue@gmail.com
> Sent: Saturday, February 29, 2020 12:27 PM
> To: Matan Azrad <matan@mellanox.com>; dev@dpdk.org
> Cc: Tonghao Zhang <xiangxia.m.yue@gmail.com>; stable@dpdk.org
> Subject: [dpdk-dev] [dpdk v1] net/mlx5: fix possible building error
>
> From: Tonghao Zhang <xiangxia.m.yue@gmail.com>
>
> When setting the CONFIG_RTE_BUILD_SHARED_LIB to y, and build the mlx5
> pmd, there is a building error.
> To fix it, add RTE_IBVERBS_LINK_DLOPEN to include relative codes.
>
> > mlx5_common.o: In function `mlx5_glue_init':
> > drivers/common/mlx5/mlx5_common.c:324: undefined reference to
> `dlclose'
>
> Fixes: 7b4f1e6bd367 ("common/mlx5: introduce common library")
> Cc: stable@dpdk.org
>
> Signed-off-by: Tonghao Zhang <xiangxia.m.yue@gmail.com>
> ---
> drivers/common/mlx5/mlx5_common.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
I test this case on multiple environments and don't see the build failure. Can you please provide more information about yours, and how to reproduce this?
Thanks,
Ali
next prev parent reply other threads:[~2020-03-01 17:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 10:27 xiangxia.m.yue
2020-03-01 17:09 ` Ali Alnubani [this message]
2020-03-02 0:22 ` Tonghao Zhang
2020-03-02 7:35 ` Ali Alnubani
2020-03-02 8:13 ` Tonghao Zhang
2020-03-02 9:47 ` Ali Alnubani
2020-03-02 10:56 ` Tonghao Zhang
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=AM0PR05MB44015925E9C55C483B52FB1BD7E60@AM0PR05MB4401.eurprd05.prod.outlook.com \
--to=alialnu@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=stable@dpdk.org \
--cc=xiangxia.m.yue@gmail.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).