[dpdk-dev] [PATCH v10 1/1] net/af_xdp: introduce AF XDP PMD driver

Ye Xiaolong xiaolong.ye at intel.com
Thu Apr 4 10:40:31 CEST 2019


On 04/04, Luca Boccassi wrote:
>> 
>> After apply the fix in af_xdp pmd's meson.build, now I was able to
>> build
>> library for af_xdp pmd.
>> 
>> $ ls drivers/ |grep xdp
>> a715181@@rte_pmd_af_xdp at sha
>> a715181@@rte_pmd_af_xdp at sta
>> a715181@@tmp_rte_pmd_af_xdp at sta
>> librte_pmd_af_xdp.a
>> librte_pmd_af_xdp.so
>> librte_pmd_af_xdp.so.1
>> librte_pmd_af_xdp.so.1.1
>> libtmp_rte_pmd_af_xdp.a
>> rte_pmd_af_xdp.pmd.c
>> 
>> But I found that if I install libbpf to /usr/local/lib64 by default,
>> application
>> built by meson build will fail to run:
>> 
>> $ ./dpdk-testpmd
>> ./dpdk-testpmd: error while loading shared libraries: libbpf.so.0:
>> cannot open shared object file: No such file or directory
>> 
>> While install libbpf to /usr/lib doesn't have this issue (I was
>> testing on ubuntu system).
>> Is it a expected behavior? Do we need any fix for it?
>
>Hi,
>
>That is expected and distro specific: if your distro doesn't add
>/usr/local/lib* to the compiler path, it also won't be in the
>LD_LIBRARY_PATH.
>
>So if you do:
>
>LD_LIBRARY_PATH=/usr/local/lib64 ./dpdk-testpmd

Yes, it does work for me.

>
>It should then work. It's not related to the build system, but just to
>what the default paths are in the distro.

Thanks for confirmation, then I can send my v11 out :)

Thanks,
Xiaolong
>
>-- 
>Kind regards,
>Luca Boccassi


More information about the dev mailing list