On Fri, Feb 14, 2025 at 09:30:38AM +0100, David Marchand wrote:
> Hello,
>
> On Thu, Feb 13, 2025 at 6:47 PM David Aldrich
> <david.aldrich.n...@gmail.com> wrote:
> >
> > I would be grateful for some help please. I am building a 3rd party
> > application that I believe was linked against DPDK 20.11.10.
> >
> > I built this DPDK version using:
> >
> > $ meson setup -Dexamples=l2fwd,helloworld build --reconfigure
> >
> > When I build the 3rd party application I get link errors:
> >
> > /usr/bin/ld: cannot find -lrte_pmd_bond: No such file or directory
> > /usr/bin/ld: cannot find -lrte_pmd_vmxnet3_uio: No such file or directory
> > /usr/bin/ld: cannot find -lrte_pmd_i40e: No such file or directory
> > /usr/bin/ld: cannot find -lrte_pmd_ixgbe: No such file or directory
> > /usr/bin/ld: cannot find -lrte_pmd_e1000: No such file or directory
> > /usr/bin/ld: cannot find -lrte_pmd_ring: No such file or directory
> >
> > I can see librte_pmd_e1000.a in my build for DPDK 19.11 but not in 20.11.
> >
> > Are these libraries supported by 20.11? If so, how should I build them?
>
> Drivers binaries have been renamed during 20.11.
> See a20b2c01a7a1 ("build: standardize component names and defines").
>
> In your dpdk 20.11 build, look for rte_net_e1000.a.
>
> (Note that I suspect that this 3rd party application will have more
> issues than just linking. I suggest you look at the API/ABI changes
> sections in the v20.11 release notes)
>
As a general comment, when linking DPDK it is strongly recommend that you
using pkg-config (or pkgconf) to get the linker libraries and arguments.
It's not infrequent that new libraries would be added, removed or renamed
in DPDK, so by using pkgconfig you should always get the correct lib and
driver list for the DPDK release you are linking against.
Regards,
/Bruce
