Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Danny Wood <danny@rotronics.co.uk>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>,
	"May, Torsten" <torsten.may@ebee.de>
Subject: Re: [Buildroot] OpenSSL v3.0
Date: Mon, 10 Jul 2023 00:15:37 +0200	[thread overview]
Message-ID: <87sf9wybna.fsf@48ers.dk> (raw)
In-Reply-To: <d23d2495-f724-98b8-1f09-23a3914f3510@rotronics.co.uk> (Danny Wood's message of "Thu, 22 Jun 2023 10:24:28 +0100")

>>>>> "Danny" == Danny Wood <danny@rotronics.co.uk> writes:

 > On 19/06/2023 14:26, Peter Korsgaard wrote:
 >>>>>>> "May," == May, Torsten <torsten.may@ebee.de> writes:
 >> > Hi Peter,
 >> > as September is approaching quickly, is there any progress on that topic?
 >> 
 >> Unfortunately not. So far no patches for openssl 3.x have been
 >> submitted.
 >> 
 >> If you are using openssl then now would be a VERY good time to
 >> contribute an update to the 3.x series.
 >> 

 > Hi,

 > Attached is a patch I have made to build v3.0.9 of OpenSSL (LTS until 2026).

 > Everything in my build tree compiled fine with the new version apart
 > from MariaDB which also needed updating, attached is an additional
 > patch which updates MariaDB to v10.11.4 (LTS until 2026)

 > These both apply on top of the 2023.02.2 buildroot tar balls.

 > I have been running these updated packages for a couple of days and
 > haven't had any issues so far.

Committed the mariadb bump to master after fixing the README.md hash,
thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-07-09 22:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19 12:46 [Buildroot] OpenSSL v3.0 May, Torsten
2023-06-19 13:26 ` Peter Korsgaard
2023-06-22  9:24   ` Danny Wood
2023-07-09 22:15     ` Peter Korsgaard [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2023-02-08 19:44 Afshin Pir
2023-02-09  6:54 ` 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=87sf9wybna.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=danny@rotronics.co.uk \
    --cc=torsten.may@ebee.de \
    /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