From: Robin Jarry <rjarry@redhat.com>
To: dev@dpdk.org
Subject: [PATCH dpdk v2 0/2] Fix dynamic link of driver symbols with pkgconf
Date: Thu, 15 Oct 2026 13:26:08 +0200 [thread overview]
Message-ID: <20261015112607.3008792-4-rjarry@redhat.com> (raw)
In-Reply-To: <20261015100921.2944274-5-rjarry@redhat.com>
When building against dynamic libraries using pkg-config, linking fails
because symbols exposed by drivers are not found:
/usr/bin/x86_64-linux-gnu-ld.bfd: ....o:(.data.rel.ro+0x148):
undefined reference to `rte_pci_dump'
That symbol is in librte_bus_pci.so which is *not* listed in the libs
section of the pkg-config file.
This series is about fixing this.
v2: Added missing update to dpdk_libraries for pkg-config
Robin Jarry (2):
meson: rename static drivers list
meson: add drivers to dynamic libraries
app/meson.build | 2 +-
buildtools/pkg-config/meson.build | 2 +-
buildtools/subproject/meson.build | 2 +-
drivers/meson.build | 6 +++++-
examples/meson.build | 2 +-
meson.build | 2 +-
6 files changed, 10 insertions(+), 6 deletions(-)
--
2.56.0
next prev parent reply other threads:[~2026-10-15 11:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 10:09 [PATCH dpdk 0/2] Fix dynamic link of driver symbols with pkgconf Robin Jarry
2026-10-15 10:09 ` [PATCH dpdk 1/2] meson: rename static drivers list Robin Jarry
2026-10-15 10:36 ` Bruce Richardson
2026-10-15 10:09 ` [PATCH dpdk 2/2] meson: add drivers to dynamic libraries Robin Jarry
2026-10-15 10:40 ` Bruce Richardson
2026-10-15 10:41 ` [PATCH dpdk 0/2] Fix dynamic link of driver symbols with pkgconf Bruce Richardson
2026-10-15 11:27 ` Robin Jarry
2026-10-15 11:26 ` Robin Jarry [this message]
2026-10-15 11:26 ` [PATCH dpdk v2 1/2] meson: rename static drivers list Robin Jarry
2026-10-15 11:26 ` [PATCH dpdk v2 2/2] meson: add drivers to dynamic libraries Robin Jarry
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=20261015112607.3008792-4-rjarry@redhat.com \
--to=rjarry@redhat.com \
--cc=dev@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