16/12/2020 22:36, lir...@marvell.com:
> From: Liron Himi <lir...@marvell.com>
>
> With pkg-config support available within musdk library
> (from musdk-release-SDK-10.3.5.0-PR2 version),
> meson option 'lib_musdk_dir' can be removed.
> PKG_CONFIG_PATH environment variable should be set appropriately
> to use the musdk library.
Sorry, it does not work.
First, when installing MUSDK, the .pc file is not updated
with the correct prefix path:
make install DESTDIR=$(readlink -f install)
In install/mv/lib/pkgconfig/libmusdk.pc:
prefix=/mv
instead of:
prefix=/musdk_path/install/mv
Second, after manually fixing the prefix path and compiling DPDK:
In file included from musdk/install/mv/include/mv_std.h:101,
from musdk/install/mv/include/drivers/mv_neta.h:100,
from dpdk/drivers/net/mvneta/mvneta_ethdev.h:24,
from dpdk/drivers/net/mvneta/mvneta_rxtx.h:10,
from dpdk/drivers/net/mvneta/mvneta_rxtx.c:7:
musdk/install/mv/include/env/mv_autogen_build_assert.h:43:5: error:
"MVCONF_DMA_PHYS_ADDR_T_SIZE" is not defined, evaluates to 0 [-Werror=undef]
musdk/install/mv/include/env/mv_autogen_build_assert.h:44:2: error:
#error "MVCONF_DMA_PHYS_ADDR_T_SIZE must match size used during musdk_lib
compilation."
The CFLAGS may be incomplete:
Cflags: -I${includedir} -DMVCONF_TYPES_PUBLIC
-DMVCONF_DMA_PHYS_ADDR_T_PUBLIC
I fixed it by adding:
-DMVCONF_DMA_PHYS_ADDR_T_SIZE=64
Please could you fix MUSDK quickly?
I think I will pull next-net as is, but I consider it is broken.
