-
-
Notifications
You must be signed in to change notification settings - Fork 749
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mismatched Rust types at X509 bindings with BoringSSL on Windows 10 #2119
Comments
@sfackler do you remember why the cast is written in that strange way? Otherwise I'll probably just rewrite it to go via |
No, that cast seems suspicious to me as well. |
fixes #2119 -- use ErrorStack abstraction in X.509 error handling
Now the
|
The |
I don't need it, I thought it was another compiler error. So it's fixed, thanks! |
Great!
…On Wed, Dec 6, 2023 at 4:45 PM Heraldo Lucena ***@***.***> wrote:
I don't need it, I thought it was another compiler error. So it's fixed,
thanks!
—
Reply to this email directly, view it on GitHub
<#2119 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAGBEREG3T3JLB2J2AYITYIDROHAVCNFSM6AAAAABAJ7YDXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBTG4ZTSNRQGY>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
--
All that is necessary for evil to succeed is for good people to do nothing.
|
Regression introduced in sfackler#2119. Ideally, tests would not leave other errors behind. Fixes sfackler#2146
Regression introduced in sfackler#2119. Ideally, tests would not leave other errors behind. Fixes sfackler#2146
I am getting the following compiler error when trying to link rust-openssl against BoringSSL (commit
f78fe19fc98e0e6f760e05c6b9d48725004700d0
, same from CI) on Windows 10:My Rust version is:
The text was updated successfully, but these errors were encountered: