From: Peter Korsgaard <peter@korsgaard.com>
To: Afshin Pir <Afshin.Pir@gallagher.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] OpenSSL v3.0
Date: Thu, 09 Feb 2023 07:54:52 +0100 [thread overview]
Message-ID: <87mt5nfhvn.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <SY2PR01MB27781C2BC99C40BB9F67F69E94D89@SY2PR01MB2778.ausprd01.prod.outlook.com> (Afshin Pir's message of "Wed, 8 Feb 2023 19:44:51 +0000")
>>>>> "Afshin" == Afshin Pir <Afshin.Pir@gallagher.com> writes:
> Hi
> I wonder whether buildroot currently working on OpenSSL v3.0 package
> def or not. If not, what are the challenges for building this package?
> Because I need to migrate to OpenSSL v3.0 in my buildroot and I like
> to know how I can do it.
There has been various discussions but currently no concrete patches for
openssl 3.0 support. Most likely not all packages will work with openssl
3.0, so we might need to keep the current openssl 1.1 package for a bit
and offer openssl 3.0 as a separate package.
Openssl 1.1.x indeed goes EOL in September, so it would be great if
someone could work on it soon!
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-02-09 6:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 19:44 [Buildroot] OpenSSL v3.0 Afshin Pir
2023-02-09 6:54 ` Peter Korsgaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-19 12:46 May, Torsten
2023-06-19 13:26 ` Peter Korsgaard
2023-06-22 9:24 ` Danny Wood
2023-07-09 22:15 ` Peter Korsgaard
2023-07-14 10:29 ` Konrad Gräfe
[not found] ` <09666051-9013-f88c-b7cb-b46abe5dbd43__38194.5088667393$1689330625$gmane$org@gateware.de>
2023-07-14 16:42 ` Bernd Kuhls
[not found] ` <d23d2495-f724-98b8-1f09-23a3914f3510__44327.5294079044$1687426363$gmane$org@rotronics.co.uk>
2023-07-14 16:24 ` Bernd Kuhls
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=87mt5nfhvn.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=Afshin.Pir@gallagher.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox