From: Alexander Egorenkov <egorenar@linux.ibm.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/s390-tools: add zlib dependency
Date: Tue, 20 Oct 2020 12:39:04 +0200 [thread overview]
Message-ID: <20201020103904.1529898-1-egorenar@linux.ibm.com> (raw)
zlib is required to build s390-tools and cannot be disabled for now
due to libvmdump.
Fixes:
$BUILD_DIR/host/bin/s390x-buildroot-linux-gnu-g++ ... -c vmdump_convert.cpp -o vmdump_convert.o
lkcd_dump.cpp:15:10: fatal error: zlib.h: No such file or directory
15 | #include <zlib.h>
| ^~~~~~~~
compilation terminated.
Signed-off-by: Alexander Egorenkov <egorenar@linux.ibm.com>
---
package/s390-tools/Config.in | 1 +
package/s390-tools/s390-tools.mk | 1 +
2 files changed, 2 insertions(+)
diff --git a/package/s390-tools/Config.in b/package/s390-tools/Config.in
index a553b5eeab..4aede4e265 100644
--- a/package/s390-tools/Config.in
+++ b/package/s390-tools/Config.in
@@ -7,6 +7,7 @@ config BR2_PACKAGE_S390_TOOLS
depends on BR2_s390x
depends on BR2_INSTALL_LIBSTDCPP
depends on BR2_TOOLCHAIN_USES_GLIBC
+ select BR2_PACKAGE_ZLIB
help
Tools for use with the s390 Linux kernel and device drivers.
diff --git a/package/s390-tools/s390-tools.mk b/package/s390-tools/s390-tools.mk
index 4d4c8188fe..d186f85cd3 100644
--- a/package/s390-tools/s390-tools.mk
+++ b/package/s390-tools/s390-tools.mk
@@ -8,6 +8,7 @@ S390_TOOLS_VERSION = 2.14.0
S390_TOOLS_SITE = $(call github,ibm-s390-tools,s390-tools,v$(S390_TOOLS_VERSION))
S390_TOOLS_LICENSE = MIT
S390_TOOLS_LICENSE_FILES = LICENSE
+S390_TOOLS_DEPENDENCIES = zlib
S390_TOOLS_MAKE_OPTS = \
ARCH=$(BR2_ARCH) \
--
2.26.2
next reply other threads:[~2020-10-20 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 10:39 Alexander Egorenkov [this message]
2020-10-24 20:55 ` [Buildroot] [PATCH 1/1] package/s390-tools: add zlib dependency Thomas Petazzoni
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=20201020103904.1529898-1-egorenar@linux.ibm.com \
--to=egorenar@linux.ibm.com \
--cc=buildroot@busybox.net \
/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