-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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 enterprise linux build #84795
Fix enterprise linux build #84795
Conversation
Ensure a recent lld is available on the build host
Tagging subscribers to this area: @dotnet/ncl, @bartonjs, @vcsjones Issue DetailsEnsure a recent lld is available on the build host. Attempting to fix the issue mentioned in #84148 (comment).
|
/azp run runtime-libraries enterprise-linux |
Azure Pipelines successfully started running 1 pipeline(s). |
As it is now installed in the ubuntu-22.04 image
does perhaps Ubuntu 22 come with a different libgss version than Ubuntu 18? |
I believe this is the same issue hit in #67353. Ubuntu 22.04 comes with openssl 3, which doesn't include md4 (except as a legacy provider) that gss-ntlmssp depends on. gss-ntlmssp was updated with a fix that lets it use the legacy provider, but the fix was released in version 1.1.0, while ubuntu 22.04 only has 0.7.0 available. Even the latest Ubuntu (22.10) only has 1.0.0. Would it be acceptable to enable the legacy provider in the openssl config for this test (this workaround: #67353 (comment))? @wfurt |
Sounds reasonable to me |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTLM
I guess it is too late but I'm wondering if we could just jump to 20.04 to avoid all the OpenSSL 3 mess. |
Ensure a recent lld is available on the build host. See dotnet/dotnet-buildtools-prereqs-docker#843.
Attempting to fix the issue mentioned in #84148 (comment).
Fixes #85035