From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH] doc/rel_notes: add note on libarchive dependencies
Date: Thu, 9 Nov 2023 10:52:04 +0000 [thread overview]
Message-ID: <20231109105204.12944-1-bruce.richardson@intel.com> (raw)
Since DPDK now registers an explicit dependency on libarchive, rather
than just putting -larchive in link args, we need to add a documentation
note about potential missing dependencies when static linking.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
doc/guides/rel_notes/release_23_11.rst | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/doc/guides/rel_notes/release_23_11.rst b/doc/guides/rel_notes/release_23_11.rst
index ff28083e1c..0b33665868 100644
--- a/doc/guides/rel_notes/release_23_11.rst
+++ b/doc/guides/rel_notes/release_23_11.rst
@@ -75,6 +75,16 @@ New Features
which also added support for standard atomics
(Ref: https://releases.llvm.org/3.6.0/tools/clang/docs/ReleaseNotes.html)
+* **Extra dependencies when linking against libarchive**
+
+ When the libarchive development package is present on the system,
+ DPDK will use libarchive and register a dependency on it.
+ However, on a number of Linux distributions, including, for example, Fedora and Ubuntu,
+ installing the libarchive dev package does not cause all required dependencies for static linking to be automatically installed too.
+ These additional dev packages, such as ``liblz4-dev`` and ``libacl1-dev`` on Ubuntu,
+ will need to be installed manually (if not already present)
+ to prevent errors with linking against DPDK static libraries.
+
* **Added new build options.**
* Enabling deprecated libraries is now done using
--
2.39.2
next reply other threads:[~2023-11-09 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 10:52 Bruce Richardson [this message]
2023-11-24 13:50 ` David Marchand
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=20231109105204.12944-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.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;
as well as URLs for NNTP newsgroup(s).