From: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] rust: Upgrade 1.96.1 -> 1.97.1
Date: Thu, 13 Aug 2026 13:05:18 +0200 [thread overview]
Message-ID: <b33742e3-d23b-4a8d-afe2-11379a5e6083@est.tech> (raw)
In-Reply-To: <CANNYZj9cTUg+Q5JF3GcpXGVOtNHn_TYvKUjj4mQdsyVfiBjLRA@mail.gmail.com>
On 2026-08-13 12:52, Alexander Kanavin wrote:
> On Thu, 13 Aug 2026 at 12:48, Jaipaul Cheernam via
> lists.openembedded.org
> <jaipaul.cheernam=est.tech@lists.openembedded.org> wrote:
>> I see this patch got "Changes Requested" on patchwork — do you know what needs to be fixed?
>> I'm asking because I'm upgrading OpenSSL to 4.0.1 and cargo-native fails to build without Rust 1.97.1 (the vendored openssl-sys in 1.96.1 doesn't support OpenSSL 4.x).
> This is not related to rust, but last time I tried to add openssl 4.x,
> that quickly ran into python support issues, as currently released
> python does not support openssl 4.x even in the latest commit on the
> stable branch, and we need to wait for a new major release sometime in
> the autumn. Did you check that? Has the situation changed?
> Hi Alex,
Yes, I ran into the same Python issue. Python 3.14.7 fails to build _ssl
against OpenSSL 4.0.
The backport PR (#146403) was closed without merge. it looks like
they're only targeting main (3.15).
I've included it as a backport patch(CPython main 3364e7e62fa2) in my
series.
Alone with Python, I also had to fix:
- socat: two-line fix for ASN1_STRING made opaque (sent upstream)
- openssl recipe cleanup for deprecated engines
- Rust/cargo-native: needs 1.97.1 for openssl-sys 0.9.114 which
adds OpenSSL 4.0 support
Happy to share the series if you want to take a look.
Regards,
Jaipaul
prev parent reply other threads:[~2026-08-13 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 9:19 [PATCH] rust: Upgrade 1.96.1 -> 1.97.1 Deepesh.Varatharajan
2026-08-13 10:48 ` Jaipaul Cheernam
2026-08-13 10:52 ` [OE-core] " Alexander Kanavin
2026-08-13 11:05 ` Jaipaul Cheernam [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=b33742e3-d23b-4a8d-afe2-11379a5e6083@est.tech \
--to=jaipaul.cheernam@est.tech \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.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 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.