From: David Aldrich <david.aldrich.ntml@gmail.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: David Marchand <david.marchand@redhat.com>, users <users@dpdk.org>
Subject: Re: Build of DPDK 20.11.10 is missing some libraries
Date: Fri, 14 Feb 2025 09:33:40 +0000 [thread overview]
Message-ID: <CAJK_iehA8t-Rdoym709zZrp-vkijpFDSaDZfXeB2DP6-XUB6cA@mail.gmail.com> (raw)
In-Reply-To: <Z68HsAsU-rtRIVf7@bricha3-mobl1.ger.corp.intel.com>
Hi Bruce and David
Thank you for your helpful answers.
Best regards
David
On Fri, Feb 14, 2025 at 9:07 AM Bruce Richardson
<bruce.richardson@intel.com> wrote:
>
> 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.ntml@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
prev parent reply other threads:[~2025-02-14 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 17:47 David Aldrich
2025-02-14 8:30 ` David Marchand
2025-02-14 9:06 ` Bruce Richardson
2025-02-14 9:33 ` David Aldrich [this message]
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=CAJK_iehA8t-Rdoym709zZrp-vkijpFDSaDZfXeB2DP6-XUB6cA@mail.gmail.com \
--to=david.aldrich.ntml@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=users@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).