Package: libkdumpfile / 0.5.5-2

Metadata

Package Version Patches format
libkdumpfile 0.5.5-2 3.0 (quilt)

Patch series

view the series file
Patch File delta Description
kdumpid add libaddrxlat la to libs.diff | (download)

tools/kdumpid/Makefile.am | 1 1 + 0 - 0 !
1 file changed, 1 insertion(+)

 kdumpid: add libaddrxlat.la to libs
 Since util.c calls some functions from libaddrxlat, let's link against that
 library explicitly instead of relying on its being added as a dependency of
 libkdumpfile.
kdumpid unconditionally link zlib.diff | (download)

tools/kdumpid/Makefile.am | 4 4 + 0 - 0 !
1 file changed, 4 insertions(+)

 kdumpid: unconditionally link with zlib
 Since uncompress_config() uses functions from zlib, kdumpid must link with
 ZLIB. It may work without it, because ZLIB is often added as a dependency
 for libbfd, but we should not rely on it.
no python.diff | (download)

Makefile.am | 3 0 + 3 - 0 !
configure.ac | 4 0 + 4 - 0 !
2 files changed, 7 deletions(-)

 fully disable building legacy python bindings
 We are already disabling it, but it looks like distclean still
 tries to use the Python directory, which then fails.
 Backport the necessary parts of the commit removing the legacy
 bindings to disable this fully.
fix parallel pti user test exec.diff | (download)

tests/xlat-linux-x86_64-6.11-pti-user-ver | 2 1 + 1 - 0 !
tests/xlat-os-common | 11 6 + 5 - 0 !
2 files changed, 7 insertions(+), 6 deletions(-)

 fix xlat-linux-x86_64-6.11-pti-user-ver with parallel
 runs
 The xlat-linux-x86_64-6.11-pti-user and xlat-linux-x86_64-6.11-pti-user-ver
 test cases use the same input files, but the logic is flawed, because they
 also use the same output file names. That fails if both run in parallel.