From: Stephen Hemminger <stephen@networkplumber.org>
To: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: tailqs issue
Date: Wed, 19 Mar 2025 16:16:59 -0700 [thread overview]
Message-ID: <20250319161659.573e9660@hermes.local> (raw)
In-Reply-To: <CH3PR01MB8470103A17A1A2C7D3CC81EB8FD92@CH3PR01MB8470.prod.exchangelabs.com>
On Wed, 19 Mar 2025 21:52:39 +0000
"Lombardo, Ed" <Ed.Lombardo@netscout.com> wrote:
> Hi Stephen,
> I added the fib library, but I now see there are many more dpdk libraries I need to add. Is this typically the case with the example files working with primary DPDK application?
>
> I am using meson and ninja to build the examples, but I don't know how to know the library dependencies.
>
> How do I learn ahead of building my Application as to what extra libraries I need to include for the DPDK example to work?
>
> I am doing incremental build-test-find_missing_library.
>
> So far, I needed to add these: -lrte_fib -lrte_rib -lrte_stack -lrte_member -lrte_efd
>
> Thanks,
> Ed
The typical case is to make sure that primary and secondary are built with the same libraries.
next prev parent reply other threads:[~2025-03-19 23:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 17:50 Lombardo, Ed
2025-03-19 20:23 ` Stephen Hemminger
2025-03-19 21:52 ` Lombardo, Ed
2025-03-19 23:16 ` Stephen Hemminger [this message]
2025-03-21 18:18 ` Lombardo, Ed
2025-03-24 5:01 ` Lombardo, Ed
2025-03-24 14:59 ` Kompella V, Purnima
2025-03-24 16:39 ` Lombardo, Ed
2025-03-25 10:25 ` Kompella V, Purnima
2025-03-25 14:39 ` Lombardo, Ed
2025-03-25 22:20 ` Stephen Hemminger
2025-03-25 22:24 ` Lombardo, Ed
2025-03-25 22:41 ` Stephen Hemminger
2025-03-25 22:56 ` Lombardo, Ed
2025-03-26 10:27 ` Kompella V, Purnima
2025-03-26 14:14 ` Stephen Hemminger
2025-03-26 14:33 ` Kompella V, Purnima
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=20250319161659.573e9660@hermes.local \
--to=stephen@networkplumber.org \
--cc=Ed.Lombardo@netscout.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).