-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Fix ./build.sh --portableBuild false #50097
Conversation
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
9227ad5
to
97c21fa
Compare
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsNon-portable builds are used by source-build and also use for testing/debugging things, like trying out OpenSSL 3.0: Fixes: #43219 Should I add a CI run that verifies
|
cc @ViktorHofer for that question. |
FWIW, having a CI leg for this would have caught #42415 sooner |
I can't tell if the |
97c21fa
to
f78f38b
Compare
f78f38b
to
f87df0c
Compare
f87df0c
to
0716d25
Compare
Can someone please review this? The test failures look unrelated to my changes. |
I think we should have a non portable build in CI to protect that scenario. Unsure if per PR or as a rolling build. |
|
So we probably wanna do this as part of this PR now as the other change is already merged? |
0716d25
to
f015252
Compare
Thanks a lot @omajid |
Hey, @bartonjs, this new CI run is failing on CentOS 7 (with OpenSSL 1.0 non-portable):
The errors look like this:
Are these known issues? |
I was originally going to say "sort of, I saw and fixed this in #51155". But that appears to be untrue. #define EVP_PKEY_get0_RSA local_EVP_PKEY_get0_RSA belongs right above runtime/src/libraries/Native/Unix/System.Security.Cryptography.Native/opensslshim.h Line 1120 in ee07190
|
Actually, since there's also a PSS_SALTLEN problem it requires slightly more surgery. (The "define if missing" needs to move up to before the "#if portable") |
5e11bfc
to
c9e2a17
Compare
@omajid Looks like you didn't quite move it high enough. If you pull the newer main you should be able to get rid of the PSS_SALTLEN move (since I already did it and it's now a conflict), but adding the missing |
Non-portable builds are used by source-build and also use for testing/debugging things, like trying out OpenSSL 3.0: dotnet#46526 (comment) Fixes: dotnet#43219
c9e2a17
to
4fa7e11
Compare
Non-portable builds are used by source-build and also useful for testing/debugging things, like trying out OpenSSL 3.0:
#46526 (comment)
Fixes: #43219
Should I add a CI run that verifies
./build.sh --portableBuild false
works?