From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: buildroot@buildroot.org
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>,
Alexander Egorenkov <egorenar@linux.ibm.com>
Subject: [Buildroot] [PATCH 1/1] package/s390-tools: needs OpenSSL-enabled libcurl
Date: Sat, 18 Mar 2023 13:30:58 +0100 [thread overview]
Message-ID: <20230318123058.4103-1-fontaine.fabrice@gmail.com> (raw)
Fix the following build failure raised bump to version 2.17.0 in commit
eab9110afbef9c39569c4cc988aed15c48f7ce44 and
https://github.com/ibm-s390-linux/s390-tools/commit/56fecf1832c3ebc4626ddf5c598762833c362d5e:
Error: libcurl is not built with the OpenSSL backend
Fixes:
- http://autobuild.buildroot.org/results/32aa8f0bece5da2a16d761f175d46c7d3e0a8965
- http://autobuild.buildroot.org/results/535253f483c927da456c0be292df6a58c1f39737
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
---
package/s390-tools/s390-tools.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/package/s390-tools/s390-tools.mk b/package/s390-tools/s390-tools.mk
index 8cd5491405..ec01a18cb0 100644
--- a/package/s390-tools/s390-tools.mk
+++ b/package/s390-tools/s390-tools.mk
@@ -14,7 +14,7 @@ S390_TOOLS_MAKE_OPTS = \
ARCH=$(BR2_ARCH) \
CFLAGS="$(TARGET_CFLAGS) -D_GNU_SOURCE"
-ifeq ($(BR2_PACKAGE_LIBCURL),y)
+ifeq ($(BR2_PACKAGE_LIBCURL_OPENSSL),y)
S390_TOOLS_DEPENDENCIES += libcurl
S390_TOOLS_MAKE_OPTS += \
CURL_CONFIG=$(STAGING_DIR)/usr/bin/curl-config \
--
2.39.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-03-18 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 12:30 Fabrice Fontaine [this message]
2023-03-18 21:21 ` [Buildroot] [PATCH 1/1] package/s390-tools: needs OpenSSL-enabled libcurl Thomas Petazzoni via buildroot
2023-03-19 19:34 ` Peter Korsgaard
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=20230318123058.4103-1-fontaine.fabrice@gmail.com \
--to=fontaine.fabrice@gmail.com \
--cc=buildroot@buildroot.org \
--cc=egorenar@linux.ibm.com \
/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).