From: "Jaipaul Cheernam" <jaipaul.cheernam@est.tech>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] rust: Upgrade 1.96.1 -> 1.97.1
Date: Thu, 13 Aug 2026 03:48:08 -0700 [thread overview]
Message-ID: <1500499.1786618088330989780@lists.openembedded.org> (raw)
In-Reply-To: <20260717091912.1752666-1-Deepesh.Varatharajan@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
Hi Deepesh,
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).
The current Rust 1.96.1 ships openssl-sys 0.9.107 which fails when building against OpenSSL 4.0:
"This crate is only compatible with OpenSSL (version 1.1.0, 1.1.1, or 3.x)"
If there's anything I can help with to get this patch merged, happy to assist.
Regards,
Jaipaul
[-- Attachment #2: Type: text/html, Size: 740 bytes --]
next prev parent reply other threads:[~2026-08-13 10:48 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 [this message]
2026-08-13 10:52 ` [OE-core] " Alexander Kanavin
2026-08-13 11:05 ` Jaipaul Cheernam
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=1500499.1786618088330989780@lists.openembedded.org \
--to=jaipaul.cheernam@est.tech \
--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.