From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libuhttpd: fix build with wolfssl
Date: Fri, 16 Jul 2021 23:22:33 +0200 [thread overview]
Message-ID: <20210716232233.4e69ca1d@windsurf> (raw)
In-Reply-To: <20210710090633.938593-1-fontaine.fabrice@gmail.com>
On Sat, 10 Jul 2021 11:06:33 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Build with wolfssl is broken since bump to version 3.12.1 in commit
> 4d85defa7103aadc74223868fb83ed0bed144f4d:
>
> /data/buildroot-autobuilder/instance-0/output-1/build/libuhttpd-3.12.1/src/ssl/openssl.c: In function 'ssl_context_new':
> /data/buildroot-autobuilder/instance-0/output-1/build/libuhttpd-3.12.1/src/ssl/openssl.c:180:32: error: 'SSL_OP_NO_SSLv3' undeclared (first use in this function); did you mean 'WOLFSSL_OP_NO_SSLv3'?
> 180 | SSL_CTX_set_options(c, SSL_OP_NO_SSLv3 | SSL_OP_NO_TLSv1 | SSL_OP_NO_TLSv1_1);
> | ^~~~~~~~~~~~~~~
> | WOLFSSL_OP_NO_SSLv3
>
> This build failure is raised by
> https://github.com/zhaojh329/libuhttpd/commit/0fb46935f0cd5f737c6f4e6053d62268aca793a7
> as since this commit, libuhttpd expects that SSL_OP_NO_xxx are defined
> by wolfssl
>
> Fixes:
> - http://autobuild.buildroot.org/results/79e3fa697537f2e33863e490b74ec881993eae73
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/libuhttpd/Config.in | 1 +
> 1 file changed, 1 insertion(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-07-16 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 9:06 [Buildroot] [PATCH 1/1] package/libuhttpd: fix build with wolfssl Fabrice Fontaine
2021-07-16 21:22 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-04 20:23 Fabrice Fontaine
2021-08-04 20:33 ` Yann E. MORIN
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=20210716232233.4e69ca1d@windsurf \
--to=thomas.petazzoni@bootlin.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 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.