From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/pistache: fix libressl build
Date: Sat, 25 Feb 2023 22:02:54 +0100 [thread overview]
Message-ID: <20230225220254.69e933f2@windsurf> (raw)
In-Reply-To: <20230225172806.9444-1-fontaine.fabrice@gmail.com>
On Sat, 25 Feb 2023 18:28:06 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fix the following libressl build failure which is probably raised since
> the addition of the package in commit
> 65d891efc2fb069f9cf707f47302776f7076b80c:
>
> ../src/server/listener.cc: In member function 'void Pistache::Tcp::Listener::setupSSLAuth(const std::string&, const std::string&, int (*)(int, void*))':
> ../src/server/listener.cc:582:29: error: 'SSL_verify_cb' was not declared in this scope; did you mean 'RSA_verify'?
> 582 | (SSL_verify_cb)cb
> | ^~~~~~~~~~~~~
> | RSA_verify
>
> Fixes:
> - http://autobuild.buildroot.org/results/066fc078980e5216f38411eee455088e15fa1101
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> ...erver-listener.cc-fix-libressl-build.patch | 38 +++++++++++++++++++
> 1 file changed, 38 insertions(+)
> create mode 100644 package/pistache/0002-src-server-listener.cc-fix-libressl-build.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-02-25 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 17:28 [Buildroot] [PATCH 1/1] package/pistache: fix libressl build Fabrice Fontaine
2023-02-25 21:02 ` Thomas Petazzoni via buildroot [this message]
2023-03-14 8:25 ` 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=20230225220254.69e933f2@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=thomas.petazzoni@bootlin.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