From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@buildroot.org
Subject: [Buildroot] [git commit] package/uacme: ualpn needs libopenssl
Date: Mon, 15 Aug 2022 21:18:56 +0200 [thread overview]
Message-ID: <20220815191551.9C0C7876B9@busybox.osuosl.org> (raw)
commit: https://git.buildroot.net/buildroot/commit/?id=ac64086ce5f299b146c670ad4f3b63a163335ee2
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
ualpn is not compatible with libressl as stated by upstream in
https://github.com/ndilieto/uacme/commit/32546c7caa1626bbef860cf81e53d10e29fca5cb
resulting in the following build failure:
ualpn.c: In function 'ssl_client_hello_cb':
ualpn.c:2038:16: error: 'SSL_CLIENT_HELLO_RETRY' undeclared (first use in this function); did you mean 'SSL_F_CLIENT_HELLO'?
2038 | return SSL_CLIENT_HELLO_RETRY;
| ^~~~~~~~~~~~~~~~~~~~~~
| SSL_F_CLIENT_HELLO
Fixes:
- http://autobuild.buildroot.org/results/d7d49cfce6f99c59e99c8e15399164fd5ecacc21
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
---
package/uacme/Config.in | 2 ++
1 file changed, 2 insertions(+)
diff --git a/package/uacme/Config.in b/package/uacme/Config.in
index 796f54754e..2c6864871c 100644
--- a/package/uacme/Config.in
+++ b/package/uacme/Config.in
@@ -21,6 +21,8 @@ config BR2_PACKAGE_UACME_UALPN
bool "enable ualpn"
depends on BR2_TOOLCHAIN_HAS_THREADS
select BR2_PACKAGE_LIBEV
+ select BR2_PACKAGE_OPENSSL_FORCE_LIBOPENSSL \
+ if !(BR2_PACKAGE_GNUTLS || BR2_PACKAGE_MBEDTLS)
help
Build and install ualpn, the transparent proxying tls-alpn-01
challenge responder.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2022-08-15 19:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220815191551.9C0C7876B9@busybox.osuosl.org \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.