From: Ali Alnubani <alialnu@mellanox.com>
To: Tonghao Zhang <xiangxia.m.yue@gmail.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
Matan Azrad <matan@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>,
Raslan Darawsheh <rasland@mellanox.com>
Subject: Re: [dpdk-dev] [dpdk v1] net/mlx5: fix possible building error
Date: Mon, 2 Mar 2020 09:47:12 +0000 [thread overview]
Message-ID: <AM0PR05MB4401A7C11A348BE0BD2CEC71D7E70@AM0PR05MB4401.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <CAMDZJNVZoCAWRbGaFgsWYnHj=vfkCOi_L3PgM8LMT0sgBdgBOQ@mail.gmail.com>
> > Do you mind sharing which OS are you using, which gcc/clang version,
> whether you have MLNX_OFED or rdma-core installed, and which version?
> 1. CentOS Linux release 7.6.1810 (Core)
> 2. kernel 3.10.0-957.1.3.el7.x86_64
> 3. OFED 4.7-3.2.9
> 4. FW 16.26.4012
> 5. gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36) 6. build the dpdk with x86_64-
> native-linuxapp-gcc
Thanks for sharing this information, still can't reproduce though:
"""
[root@hostname dpdk-next-net]# cat /etc/redhat-release
CentOS Linux release 7.6.1810 (Core)
[root@hostname dpdk-next-net]# ofed_info -s
MLNX_OFED_LINUX-4.7-3.2.9.0:
[root@hostname dpdk-next-net]# gcc --version | head -1
gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-39)
[root@hostname dpdk-next-net]# git log -1 --oneline
d7142fb version: 20.02
[root@hostname dpdk-next-net]# git diff -U0
diff --git a/config/common_base b/config/common_base
index 7ca2f28..4bd5126 100644
--- a/config/common_base
+++ b/config/common_base
@@ -60 +60 @@ CONFIG_RTE_ENABLE_LTO=n
-CONFIG_RTE_BUILD_SHARED_LIB=n
+CONFIG_RTE_BUILD_SHARED_LIB=y
@@ -366 +366 @@ CONFIG_RTE_LIBRTE_MLX4_DEBUG=n
-CONFIG_RTE_LIBRTE_MLX5_PMD=n
+CONFIG_RTE_LIBRTE_MLX5_PMD=y
[root@hostname dpdk-next-net]# make install T=x86_64-native-linuxapp-gcc -j$(nproc --all) > /dev/null
[root@hostname dpdk-next-net]# echo $?
0
"""
Anyway, I ran some tests on the patch and don't see any regressions.
One small issue though, the script check-git-log.sh is failing:
"""
./devtools/check-git-log.sh -1
Wrong headline prefix:
net/mlx5: fix possible building error
"""
You could use common/mlx5 instead of net/mlx5.
Tested-by: Ali Alnubani <alialnu@mellanox.com>
Thanks,
Ali
next prev parent reply other threads:[~2020-03-02 9:47 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
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 [this message]
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=AM0PR05MB4401A7C11A348BE0BD2CEC71D7E70@AM0PR05MB4401.eurprd05.prod.outlook.com \
--to=alialnu@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=rasland@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).