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.richard...@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
