From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 217] DPDK-19.02 will not build when MLX4/MLX5 is enabled. In comparison DPDK 18-11 builds fine
Date: Sun, 03 Mar 2019 00:05:34 +0000 [thread overview]
Message-ID: <bug-217-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=217
Bug ID: 217
Summary: DPDK-19.02 will not build when MLX4/MLX5 is enabled.
In comparison DPDK 18-11 builds fine
Product: DPDK
Version: 19.02
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: debugnetiq1@yahoo.ca
Target Milestone: ---
Here is what I did:
- installed Mellanox OFED 4.5.1 from "sources"
wget
http://www.mellanox.com/downloads/ofed/MLNX_OFED-4.5-1.0.1.0/MLNX_OFED_LINUX-4.5-1.0.1.0-rhel7.6-x86_64.tgz
&& tar -zxf MLNX_OFED_LINUX-4.5-1.0.1.0-rhel7.6-x86_64.tgz
cd MLNX_OFED_LINUX-4.5-1.0.1.0-rhel7.6-x86_64.tgz
./mlnxofedinstall --dpdk --upstream-libs --add-kernel-support
--enable-mlnx_tune
This builds and installs all userland OFED components, then installing the kmod
drivers
cd
/tmp/MLNX_OFED_LINUX-4.5-1.0.1.0-3.10.0-957.5.1.el7.x86_64/MLNX_OFED_LINUX-4.5-1.0.1.0-rhel7.6-ext/RPMS
&& yum install
mlnx-ofa_kernel-modules-4.5-OFED.4.5.1.0.1.1.gb4fdfac.kver.3.10.0_957.5.1.el7.x86_64.x86_64.rpm
Now building dpdk-19.02
- download, untar then enable in ./config/common_base
CONFIG_RTE_LIBRTE_MLX4_PMD=y and CONFIG_RTE_LIBRTE_MLX5_PMD="y"
export DPDK_DIR=/opt/dpdk_install/dpdk-19.02
cd $DPDK_DIR
export DPDK_BUILD=$DPDK_DIR/install
export RTE_SDK=$DPDK_DIR
export DPDK_TARGET=x86_64-native-linuxapp-gcc
export RTE_TARGET=x86_64-native-linuxapp-gcc
make config T=$DPDK_TARGET
make install T=$DPDK_TARGET DESTDIR=install
dpdk-19.02 build fails when linking testpmd
...
== Build app
== Build app/test-pmd
Package libibverbs was not found in the pkg-config search path.
Perhaps you should add the directory containing `libibverbs.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libibverbs' found
Then in the log
LD testpmd
/opt/dpdk_install/dpdk-19.02/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx4.a(mlx4_glue.o):
In function `mlx4_glue_dv_set_context_attr':
/opt/dpdk_install/dpdk-19.02/drivers/net/mlx4/mlx4_glue.c:239: undefined
reference to `mlx4dv_set_context_attr'
/opt/dpdk_install/dpdk-19.02/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx4.a(mlx4_glue.o):
In function `mlx4_glue_dv_init_obj':
/opt/dpdk_install/dpdk-19.02/drivers/net/mlx4/mlx4_glue.c:231: undefined
reference to `mlx4dv_init_obj'
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-03-03 0:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-217-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).