From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/openssl: statically-linked openssl does not provide threads
Date: Thu, 20 Jul 2023 23:21:48 +0200 [thread overview]
Message-ID: <20230720232148.277f7bac@windsurf> (raw)
In-Reply-To: <20230720175319.151079-1-bernd@kuhls.net>
On Thu, 20 Jul 2023 19:53:18 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:
> Add blind option to mark availability of threads, needed for tor.
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
> package/openssl/Config.in | 6 ++++++
> 1 file changed, 6 insertions(+)
Meh, I don't like this very much :-/ But I admit I don't (at this time)
have a much better proposal. Reverting the problematic change from
OpenSSL? But wait, according to the issue you're pointing
(https://github.com/openssl/openssl/issues/14574), it's an OpenSSL
1.1.x issue that won't be fixed because OpenSSL 1.1.x is in maintenance
mode only. But now we're using OpenSSL 3.x so surely this issue needs
to be fixed? If that's the case, a revert of the change seems in order
for now?
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
prev parent reply other threads:[~2023-07-20 21:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 17:53 [Buildroot] [PATCH 1/2] package/openssl: statically-linked openssl does not provide threads Bernd Kuhls
2023-07-20 17:53 ` [Buildroot] [PATCH 2/2] package/tor: needs openssl with threads Bernd Kuhls
2023-07-20 21:21 ` Thomas Petazzoni via buildroot [this message]
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=20230720232148.277f7bac@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--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